Use case
To ensure that files are actually uploaded during a transition (e.g., on the transition screen), this setup validates whether any new attachments were added.
⚒️ Configuration
Jira expression*
issue.attachments.filter(attachment => attachment.id == null).length > 0
This expression checks for attachments that are present but don’t yet have an ID, which indicates they were uploaded during the transition.
Attachments added during the transition are already included in issue.attachments, but they do not yet have an id at the time the validator is evaluated.
The absence of an id is used to detect newly added files and block the transition if none are present.
You can refine the validation by filtering for specific file types or filenames.
For example, to allow only PDF uploads during the transition, use:
issue.attachments.filter(a => a.id == null && a.mimeType == "application/pdf").length > 0
You can also check for specific filenames:
issue.attachments.filter(a => a.id == null && a.filename.toLowerCase().includes("invoice")).length > 0
Combine multiple conditions as needed to tailor the validation to your requirements.
📚 Related use cases
| Use case | JWT feature | Workflow function | Use case description |
|---|---|---|---|
| Block a transition based on issue links |
|
Evaluate issue links and hide transitions based on the outcome. 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. |
|
| Block a transition based on sprint information |
|
Make sure that an issue is not in an active sprint. 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. |
|
| Block a transition based on the day of the week |
|
Block transitions on weekends or any other day of the week. 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. |
|
| Block a transition if a predefined field value has not been changed |
|
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. |
|
| Block a transition if some issues under an epic are not in a certain status |
|
Check whether an epic has all issues under it in a certain status. This is particularly important if you want to block an epic as long as work is still being done on related sub-tasks. 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. |
|
| Check current issue status |
|
Check whether the current issue is in a particular status. 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. |
|
| Check for unresolved sub-tasks |
|
Check whether the current issue has any unresolved sub-tasks. This is particularly important if you want to block a parent issue as long as work is still being done on related sub-tasks. 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. |
|
| Check if an attachment was added recently |
|
Make sure that the current user has uploaded a attachment during a definite period of time. 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. |
|
| Check parent issue type |
|
Check whether the parent of the current issue is of a certain issue type. This is particularly important if you want to reuse a workflow for multiple sub-task issue types but only want a transition to be available if the sub-task belongs to a certain user story or a bug. 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. |
|
| Check the number of times that a field has changed |
|
Check the number of times that a field has changed.
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. |
|
| Check whether an attachment was added during the transition. |
|
Make sure that the current user has uploaded a attachment during the transition. 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. |
|
| Evaluate the Parent field |
|
Evaluate different values of the issue in the Parent Link field of the transitioned issue. 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. |
|
| Evaluate worklogs in sub-tasks |
|
Evaluate if work has been logged in a sub-task to prevent transitioning the parent issue when no work has been logged. 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. |
|
| Validate an issue only if a comment is written during the transition |
|
Evaluate the comments and block transitions based on the outcome. This use case is only valid for validators as it involves making changes during a transition. An additional error message can be added. |
|
| Validate worklogs |
|
Evaluate if a user has logged more than a certain amount of time in the latest worklog.
|
