Statuswechsel melden
When a record's status changes, the people responsible and whoever created the record get a notification with the new status.
Flowplan Marketplace
Documents, databases, workflows, whiteboards and looks for Flowplan – shared by the community, reviewed before they go live. One click and they're in your own instance.
When a record's status changes, the people responsible and whoever created the record get a notification with the new status.
Every morning at 8:00 the workflow finds all records past their due date that are not done yet and sends the list to one person.
Before starting, imagine the project has failed: collect the reasons, pick the most likely ones, agree on countermeasures.
Short IDs of errors from monitoring like WEBAPP-3K become a link to the search in Sentry.
Issue keys like ABC-123 become a link to the issue in Jira as you type – for one or two project keys.
group/project!42 becomes a link to the merge request, group/project#7 to the issue – on gitlab.com or your own instance.
owner/repo#123 and #123 become links to issues and pull requests, abc1234 to the commit – just like on GitHub itself.
A short status report with traffic lights for schedule, budget and scope, progress, next steps and decisions needed.
Release notes for users: highlights, new, improved, fixed, important notes and upgrade steps.
Agenda and outcomes of the first project meeting: goal, roles, ground rules, risks and the first steps.
Project risks with likelihood, impact, a calculated risk score, mitigation, owner and status.
Bugs with severity, status, environment and owner – as a board, a table and with a form for reports.
Goal, scope, people and risks of a project on one page.
Kanban for two-week sprints with story points and assignees.
Topics by quarter and status, with a board and a timeline for planning.
Tasks with status, period, effort and a timeline for one project.