On this page
Use case
Evaluate a Date Picker field and block the transition if it has not been updated.
This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator.
Prerequisites
Add the post function Update fields to the transition of your choice.
Target issue*
Select current issue.
Fields
Field*
Choose a date field, e.g., Date picker, Planned end date, Planned start date, Due date...etc.
In this example, we will consider due date as our date field.
Value*
Select Set field value manually (parser expression) and enter the following expression with the date of your choice respecting this format.
1970-01-01
Configuration
Jira expression*
Compare the field code of the custom field with the date introduced previously in the Update fields post function as in the following expression.
issue.customfield_10001 != "1970-01-01"
Related use cases
Use case | JWT feature | Workflow function | Parser functions | Complexity |
---|---|---|---|---|
Block a transition based on issue links | ADVANCED | |||
Block a transition based on sprint information | BEGINNER | |||
Block a transition based on the day of the week | BEGINNER | |||
Block a transition if a predefined field value has not been changed | BEGINNER | |||
Block a transition if some issues under an epic are not in a certain status | INTERMEDIATE | |||
Check current issue status | BEGINNER | |||
Check for unresolved sub-tasks | INTERMEDIATE | |||
Check if an attachment was added recently | BEGINNER | |||
Check parent issue type | INTERMEDIATE | |||
Check the number of times that a field has changed | INTERMEDIATE | |||
Evaluate the Parent Link field | INTERMEDIATE | |||
Evaluate worklogs in sub-tasks | BEGINNER | |||
Validate an issue only if a comment is written during the transition | BEGINNER | |||
Validate worklogs |
If you still have questions, feel free to refer to our support team.