The list below contains some use cases that can be realized using JWT for Jira Cloud.
Make sure to come by once in a while since the number of use cases will grow over time.
Use cases and examples
|Use case||Type||Function||Use case description||Complexity|
|Add a sub-task's summary and key to the description of its parent||Update fields|
When a sub-task is created, its summary, issue key and date, and time of creation will be added to the description of the parent issue.
|Add comment when rejecting an issue||Add comment|
When an issue is rejected, a comment will be added to the current issue mentioning the reporter.
|Alert the assignee of important issues|
Add a comment to an issue mentioning the assignee.
The comment will only be added, if the issue priority is set to "High" or "Highest" to ensure that the assignee will only be alerted for the important issue
|Alert the reporter|
Add a simple comment to an issue mentioning the reporter.
This use case might come in handy if you don't want to use extra events in your notification schemes to notify specific users - like the reporter.
|Assign an issue to the project lead, if the issue is unassigned on creation||Update fields|
When an issue is created without an assignee selected, the issue will be assigned to the project lead of the project.
|Assign an issue to the user who last commented on it||Update fields|
Assign the issue to the user who last commented on the issue.
|Assign important issues to the project lead||Update fields|
Automatically assign and issue to the project lead.
Issues will only be re-assigned if the priority of the issue is set to Highest to make sure that only important issues are being escalated.
|Auto-transition when related issues are in a specific status||Transition issue||Automatically transition issue, if all linked issues are in specific status.|
|Block a transition based on issue links|
Evaluate issue links and hide transitions based on the outcome.
|Block a transition based on sprint information|
Make sure that an issue is not in an active sprint.
|Check current issue status|
Check whether the current issue is in a particular status.
|Check for at least one component|
Require a at least one component.
|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.
|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.
|Copy labels of a sub-task to the parent issue upon closing||Update fields||When a sub-task is closed, the labels of the sub-task will be added to the Labels field of the parent issue.|
|Create an issue in the current project||Create issue|
Create an issue in the current project and additionally set a summary.
This use case comes in handy if you quickly need to create i.e. a new bug which relates to the current issue
|Create an issue with a summary to check for attachment type||Create issue|
|Create a simple sub-task||Create issue|
Create a sub-task, set the summary based on the parent's component, and set the assignee to the current user.
|Create a story in an Epic||Create issue||Link your Epic each time you create a story.|
|Create a sub-task for high priority issues||Create issue|
Create a sub-task only if the priority of the current issue is "High".
|Create a sub-task linked to issues with a specific priority||Create issue|
|Create a sub-task mentioning the assignee when a high priority task is ready for review||Create issue|
Keep your team on track and up to date by creating a sub-task mentioning the assignee's full name and with issue links linked to the appropriate issue whenever a high priority issue has been moved to the status "Review"
|Create two sub-tasks when a user story is being approved||Create issue|
When a story is approved, two sub-tasks for Development and QA will be created.
|Escalate an issue if it is being raised with a "Blocker" priority||Transition issue|
When an issue is raised with a"Blocker" priority, a transition escalating the issue will be executed immediately after its creation.
|Fast-track transition issues assigned to the project lead||Transition issue||Automatically execute the "Start progress" transition if the issue's assignee is the project lead.|
|Keep parent's priority in sync||Update fields||Set the priority of the parent issue to the priority of the current issue.|
|Make a fix version required and add a comment|
Require a fix version and add a comment.
This use case is valid for validators.
|Make the assignee required|
Require a non empty assignee.
|Push status updates to the linked Epic||Add comment|
Add a comment to the linked Epic including the summary and status of the current issue.
This is helpful when you don't want to keep track of individual Stories and only receive notifications of the linked Epic (e.g. as a watcher or reporter).
|Push status updates to the parent||Add comment|
Add a comment to the parent issue including the summary and status of the current issue.
This is helpful when you don't want to keep track of individual sub-tasks and only receive notifications of the parent issue (e.g. as a watcher or reporter).