Set Jira Due Dates with Timer Events
Timer events make deadlines part of your process. You attach a timer to a task, and Flower sets the due date of its Jira work item. When the deadline passes, the process continues on a separate path, for example to escalate the work item or to remind someone.

Add a Timer to a Task
- Drag an intermediate event onto the border of the task, as shown in the graphic.
- Click the wrench icon and select Timer boundary event (non-interrupting), the one with the dashed border. The task stays open when the timer fires, and the timeout path starts next to it.
- In the properties panel, set Type to Duration and Value to
P3D: three days. - Connect the event to the tasks of the timeout path, for example Remind the manager in an escalation swimlane.
- Publish the model.
What You See in Jira
When the process reaches the task, Flower creates its work item with a due date three days from now. The team sees the deadline where it looks anyway: on the work item, on boards, and in filters. The process instance gets a comment Due date of … set to ….
- If the task is resolved before the due date, nothing else happens.
- If the due date passes, Flower starts the timeout path: the work item Remind the manager appears, while the original task stays open.
- If you move the due date of the work item in Jira, the timer follows it.
Flower checks timers once a day, with the timer job. A timer fires on its due day, not at an exact time.
Test It Without Waiting
You do not have to wait three days:
- Start a process instance and let Flower create the work item.
- Change the due date of the work item to today.
- As a Jira administrator, open the Flower Settings, tab Timers, and click Run timer job once.
- The timeout path starts.
Or use P0D as the value while you build the model: the timer is due at once, and the timeout path starts as soon as the process reaches the task.

More with Timers
| You want to … | Use |
|---|---|
| Remind every day while the task is open | A non-interrupting timer with a cycle, for example R-1/P1D, and a throw event on its path |
| Drop the task after a deadline | An interrupting timer boundary event (solid border): Flower cancels the work item of the task |
| Limit the time of a sub-process | A timer boundary event on the call activity |
| Wait some days in the flow | An intermediate timer event |
| Start the work later | A timer start event |
| Start a process every week | A scheduled rule of Jira Automation, not a timer |
All of these, the formats of dates and durations, what happens to the work item with an interrupting timer, the day rule, and when the timer job runs on your host are in the reference BPMN Timer Events.
What’s Next?
- BPMN Timer Events: The complete reference for timers in Flower.
- Escalate a Task with a Jira Status: Escalate by a status instead of the clock.
- Search Flower Data with JQL: Find work items with timers.
- Due date in Jira : Atlassian’s guide to due dates.

