On this page
Use case
Estimating a due date for every created issue can be time consuming. This whole process can be sped up by setting a due date based on some criterias, e.g. the associated epic.
In this use case the due date will be automatically set to a predefined value based on the selected priority.
Configuration
Add a Update fields post function to the workflow transition you want. The Create issue transition might be the best choice here.
Target issue
Choose Current issue
Fields
Choose Due date
Value
In the popup, choose the value Set field value manually (parser expression)
Expression
Enter the following expression:
%{getMatchingValue(%{issue.priority}, ["Highest", "High", "Medium", "Low"], [addDays({system.currentDateTime}, 3, RUN_AS_LOCAL), addDays({system.currentDateTime}, 5, RUN_AS_LOCAL), addDays({system.currentDateTime}, 10, RUN_AS_LOCAL), addDays({system.currentDateTime}, 20, RUN_AS_LOCAL)])}
with parsing mode set to General.
Using this expression, the due date will be set to the following value:
- If priority is Highest → Due date will be in 3 days from now
- If priority is High → Due date will be in 5 days from now
- If priority is Medium → Due date will be in 10 days from now
- If priority is Low → Due date will be in 20 days from now
- If priority is none of the above → Due date won't be updated
Related use cases
If you still have questions, feel free to refer to our support team.