Skip to content
flowplanDocumentationCommunityMarketplaceStart page

Projects and automation

Projects, tickets and sprints

Tools for teams that work with tickets – all optional: a database behaves as before until you set one of them up.

13 min readNew When is a record due?

On this page
  1. Ticket numbers
  2. Subtasks and epics
  3. When is a record done?
  4. When is a record due?New
  5. Status rules
  6. Automations
  7. Creating tasks
  8. Open in canvas: a rule becomes a workflow
  9. Scheduled automations
  10. WIP limits
  11. Sprints
  12. Time tracking
  13. Time reports and billing
  14. Records from all databases
  15. Import from Jira and Trello

Most of them sit in the … menu on the right of a database's toolbar: record templates, Automations, Status rules and done, Time report and Git connection.

More on this topic: Git and issues

Ticket numbers

A property of the type ID (ticket number) shows a running number for every record, such as WEB-123.

  • You choose the prefix when adding the property; it is unique in the workspace. A copied database, one created from a template and a restored one whose prefix has been taken meanwhile get the next free one (WEB2, WEB3, …).
  • Without a prefix Since 0.9.8: the prefix is optional – clear the field and the ID simply counts up (1, 2, 3 …). References like WEB-123 in text and Git commits only work with a prefix. Setting one later keeps the numbers (3 becomes WEB-3), and the other way round.
  • Numbers are never handed out twice, not even after deleting. A restored record keeps its number.
  • In text, WEB-123 is highlighted in every document: hovering shows title and status, ⌘/Ctrl-click opens the record. This also works for text written before the ID property existed.
  • Search finds records by their number, and Git commits can refer to them (see below).

Subtasks and epics

The type Parent record (subtasks) lets records sit below another record of the same database – for example epic → story → task. Flowplan refuses loops.

  • In the record, the Subtasks section lists everything below it with its state; you add new subtasks right there.
  • In tables, View → Show subtasks as a tree indents records and lets you fold them.
  • Subtask progress is a property of its own: it shows the share of done work across all levels as a bar.
  • On boards, Swimlanes by with the parent property gives epic swimlanes.

When is a record done?

Sprints, progress, overdue records and “My tasks” need to know when a record is done. Flowplan detects it:

  • from a status select with an option like “Done”, “Erledigt”, “Terminé”, “Fermé”, “Completato”, “Hecho” or “已完成”,
  • otherwise from a “Done” checkbox (or “Erledigt”, “Terminé” …).

Set it under … → Status rules and done when it should be different. Statuses such as “Expired”, “Expiré” or “Utilisé” do not count as done by themselves – tick them there if they should.

When is a record due? New

“My tasks”, reminders of due records (including the daily summary for chat apps and webhooks), the app's widgets and quick capture use a database's due date. Under … → Status rules and done → Due date you choose:

  • Automatic (default): a date property named like a due date – such as “Due”, “Deadline”, “Fällig”, “Échéance”, “Date limite”, “Scadenza”, “Vencimiento” or “截止日期”, then names like “Termin”, “Valid until” or “Fin de validité” –, otherwise the first date property. The option shows which one that currently is.
  • A specific date property, e.g. “Fin de validité” rather than “Date d'achat”.
  • No due date: records show without a date in “My tasks” and the widgets and trigger no due reminders.

If the chosen property is deleted, Automatic applies again.

Status rules

In the same dialog, switch on Set allowed changes and required properties:

  • Allowed changes: in the “from (row) to (column)” table, untick changes such as “Open → Done”. A record then has to be “In progress” first.
  • Required properties: a status needs certain properties – e.g. “Done only with a solution”.
  • Owners only: some statuses can only be set by people with the owner role on the database.

The rules apply everywhere: table and board, bulk edits, guests and the Git connection. A change that does not fit is refused with an explanation.

Automations

… → Automations takes care of recurring steps in the form When … only if … then …:

  • When: a record is created, a record arrives through a form, a property changes (optionally to a certain value), a date has passed or it is time according to a schedule (see Scheduled automations).
  • Only if (optional): conditions such as “Priority is High” or “Assignee is empty”.
  • Then: set properties, notify, apply a template or create a task (see Creating tasks).
    • Values for properties can be fixed, or today, now, the person who triggered it or the creator.
    • You can notify the person in a person property, the creator, the person who triggered it or a specific member.
    • Apply template puts a record template on the triggering record – with its placeholders filled in. Either only if the content is empty (existing text then stays untouched) or append below. Empty properties get the template's values. Each rule applies a template to a record only once – even if the status later goes back and forth.

Suggestions add the usual rules in one click:

  • “When Status → Done, set a date”,
  • “When the due date has passed, notify”,
  • “Assign new form records”,
  • “When Status → Approved, apply a template” (when the database has record templates).

Example: When Status changes to “Approved”, only if Company is not empty, then apply the template “Kickoff”. Every approved record gets its kickoff page with the company name and date. Applied templates are recorded in the activity log (row.template.applied).

You format the message of a notification like that of a workflow: bold, italic, underline, strikethrough, code, links, new lines, @ mentions of members (shown only – mentioned people are not notified) and formulas like $x^2$. The record's title always stays text. What the inbox, e-mail and push show is described under Notify person. Since 0.10.0

Each rule can be switched off on its own.

Creating tasks New in 0.10.2, in the :beta image

Create task turns an event into a task someone can tick off – in one of two places:

  • into the record’s document: a task with a person and a due date at the end of the record’s text or below a heading you name (made at the end if it is missing). It shows in My tasks like any task.
  • as a record in a database: a new record in a task database of your workspace. You choose which person and date properties get the person and the due date, can preset select properties such as priority or status and – if the task database has a relation to this database – link the new record to the triggering one. If the task database has a status or a done checkbox, the record shows in My tasks too.

The text takes placeholders as record templates do: “Follow up: {{Title}} ({{Status}})” is filled in with the record’s values. The person is nobody, the person in a person property of the record, the person who triggered it, the record’s creator or a specific member. Due counts days from the trigger (“+3”); empty means no due date.

Example: When Status changes to “Done”, then create the task “Write the invoice for {{Title}}” in the database “Accounting”, person “Anna”, due +2 days, linked through “Project”.

Note

A rule creates its task once per record – even if the status later goes back and forth. It acts with the rights of the person who saved it: whoever saves the rule must be allowed to create records in the task database; forms and guests still trigger it. If that right goes away later, the triggering change is refused with a message naming the rule. Records a rule creates this way run through their database’s rules once, but the tasks of those rules create nothing further – so no chain arises. Rules with “Create task” cannot be opened in the canvas yet.

Open in canvas: a rule becomes a workflow

When a rule is not enough any more – several steps, waits, approvals, AI, e-mails or other services –, the Open in canvas icon next to the rule opens it as a workflow: a workflow page next to the database with the rule as its draft. The rule keeps running until you activate the workflow; then it is replaced by a reference in the same change (“Extended as a workflow”). So both never run at once, and never neither.

The difference: a rule acts for the database, a workflow runs as the person who activates it – the activate dialog says so.

Note

Rules run on the server, however a record changes. What a rule changes does not trigger further rules, so rules cannot loop. Flowplan checks overdue records every few minutes; each rule fires once per record and date. Notifications appear as “Database automations” and can be switched off in the settings.

Scheduled automations

With the trigger it is time (schedule) a rule creates a new record regularly, for weekly reports, monthly closings or maintenance:

  • When: daily or every N days, weekly or every N weeks on a weekday, or monthly or every N months on a day (the 31st becomes the last day in shorter months), each at a time in your time zone. Examples: “Every Monday at 09:00”, “Monthly on day 1”, “Every 3 days”.
  • Then: Create a record from a record template (properties and text) or empty. Date fields can be set relative to the run, e.g. “Due: +3 days”; 0 means the same day. Or create a task as a record in a task database, such as “Standup {{Today}}” for the person who saves the rule New in 0.10.2, in the :beta image. If that fails once, the date counts as done and the message is in your inbox.

The suggestion “Create a record every Monday at 09:00” sets this up with the default template.

Note

A scheduled rule runs once per date – also after a restart – and only from the moment it was saved. Dates on which the server was not running are not made up one by one; the latest missed one runs once. The rule creates records on behalf of the person who last changed it; if they lose edit rights or the database is locked, the rule rests. Switching it on or off does not change the person.

Repeating tasks, whose next record only appears once the previous one is done, are set in the record, see Repeating tasks.

WIP limits

On a board, View → WIP limits sets a maximum per column, e.g. “In progress: 3”.

  • The column header then shows 2/3.
  • When it holds more, the column is marked.
  • With lock, the column takes no further records – wherever they come from.

Sprints

A view of the type Sprints (backlog and planning) plans work in time boxes. Set up sprints adds the “Sprint” property and the first sprint the first time.

  • Planning: drag records from the backlog into a sprint – with the mouse by the record, on touch devices hold the ⋮⋮ handle briefly and drag – or use Move to, also on phones. With the keyboard: focus the handle, press Space, choose the section with ↑/↓, Space or Enter drops, Esc cancels.
  • A sprint has a name, start, end and goal; + Sprint adds the next one.
  • Start and Complete: when completing, choose where unfinished records go – the next sprint or back to the backlog.
  • Measure size in: number of records or a number property such as story points.
  • Burndown: the running sprint shows the work left per day against the ideal line.
  • Velocity: closed sprints show what was committed and what was completed.

Time tracking

A property of the type Time tracking adds up the time worked on a record. Optionally it shows an estimate from a number property in hours next to it.

  • In the record: Start and Stop – each person has at most one running timer, a new one stops the old one.
  • Add time: a duration as 45, 1:30 or 1.5h, with a date and a note.
  • Correcting: you delete your own entries; owners can correct everyone's.
  • … → Time report: the time report of this database, switchable to the whole workspace (see Time reports and billing). The report across all databases is also under Settings → Time; there the filters carry their labels above the report, two side by side on phones.

Time reports and billing

The time report sums up the time entries of a database or of the whole workspace.

  • Period: This week (from Monday), This month, Last month or a custom period with start and end date (at most three years). The server's time zone applies.
  • Filters: person, database (in the workspace), project, billing status and billable yes/no. Project is the record a record's first relation points to (not the parent relation of subtasks) – such as the project of a task. Records without a relation are listed under No project.
  • Group by person, project, record, database, day or week. The totals come first (total, open, billed, not billable and – with hourly rates – the amount), then a bar chart and a table per group. Clicking a bar filters by that person, project or database.
  • Time entries: the single entries with date, person, record, project, note, duration and billing status (the first 1000; the export contains all).
  • Export: CSV (commas, decimal points) for spreadsheets and scripts, CSV for Excel with semicolons, decimal commas and a BOM, as a German Excel opens it correctly with a double click. Cells a spreadsheet would run as a formula start with an apostrophe.
  • Print outputs totals, chart and table (also save as PDF); expanded time entries come along.

Who sees what: everyone sees their own time entries and the entries of others on records they may read. If the permissions of the property (who may read it, see Property visibility) hide the time property from someone, they only see their own time there. Own time on a record that has become private since appears without a title as “Record without access”.

Billing status: every time entry is open, billed or not billable. Whoever may edit the record and the time property changes the status – one by one in the list of time entries, or with Mark as billed for all open entries of the current selection. Entries that are not billable stay as they are, as do running timers. Every change is in the activity log (time.billing).

Hourly rates (optional): workspace owners set a rate per person and/or per project under Hourly rates, plus the currency (e.g. EUR, CHF). A project's rate takes precedence over the person's. Members with edit rights in the workspace see amounts; readers and guests see hours only.

Through the API: GET /api/time-reports with page or workspace and the same filters (format=csv or format=excel for the files), POST /api/time-reports with { "action": "billing", "status": "billed", "filter": { … } }.

Records from all databases

My tasks shows the records of every database of the workspace that has a status or a done checkbox in one list, together with the tasks from documents (My tasks). Since 0.9.8 By default these are the open ones assigned to you – through any person property.

  • You can filter by due date and person; Source: Databases shows only records, and under Databases only: you pick databases and search text. Since 0.9.8
  • Which date counts as the due date is set per database – see When is a record due?
  • Save as view turns a filter into a personal view of its own, e.g. “All my open tickets in all projects”.

Import from Jira and Trello

Settings → Import & export → Import → Jira or Trello takes a Jira CSV export (all fields) or a Trello JSON export.

It becomes a new database with a table and a board. It brings over:

  • status or list, priority, type, labels, dates and story points,
  • assignees – as a person property when they are all members,
  • checklists, and parent issues as subtasks,
  • descriptions as content and comments as comments,
  • attachments as links (the files stay at Jira or Trello).
Was this helpful?
YesThanks!
No – tell us what's missing

Found a mistake or something missing?Edit on GitHub