Jira Misc Workflow Extensions (JMWE)

The use cases on this page provide examples of using your saved JQL Extended Search filters with JMWE – a leading Appfire automation solution available from the Atlassian Marketplace.

JMWE is an all-in-one Jira automation app to customize and expand your workflows. Its event-based actions and scheduled actions allow the scope of Jira issues to be based on a JQL query. Combining JMWE with JQL Search Extensions (JSE) means you can deliver more precise and customized automations without any additional development costs.

Event-based actions based on issue hierarchy

ParentsOfIssuesInQuery(), or ParentsOfIssuesInQueryRecursive()

When a parent issue is closed, add a comment on all matching child issues

Function: ChildrenOfIssuesInQuery(), or ChildrenOfIssuesInQueryRecursive()

In JQL Extended Search, perform a search for child issues matching a given query, for example
issue in childrenOfIssuesInQuery("project='Birch' and type=Epic and status=Closed")
Save the query as a filter. For this example, the filter is called JSE Children of Closed Epics.
In JMWE, create or edit an event-based action to use the Issue Updated event.
Set the scope to Only apply to issues that match a JQL filter.
In the JQL input box, enter the filter name, for example, filter=JSE Children of Closed Epics.
Add the Comment issues post function.
Save the action. Save the query as a filter in JSE.

JMWE use case: When a parent issue is closed, add a comment on all child issues with this information

Event-based actions based on issue links

LinkedIssueType
Searches for issues that are linked to a particular issue type, i.e. all issues that are linked to bugs
JMWE use case: For issues that are linked to bugs, when the ticket is resolved in a particular project, add a comment to the linked ticket that the development ticket (Bug) is done.
Linked IssueStatus
Searches for issues with a particular status which are linked, i.e. issues in a project which are linked to bugs in To do status.
JMWE use case: When the issue is transitioned to In Progress, for linked issues that are in “To Do” status, transition them to “In Progress”

Event-based actions based on Agile

AddedToSprintAfterStart
Searches for all issues that were added to the sprint after its start date.
JMWE use case: Create a scheduled action that sends an email every day to a team lead or a PM with a list of tickets that were added to the current sprint after the start date as information to review the unplanned items.
NextSprint
Searches for the issues that are planned for the next sprint
JMWE use case: Create a scheduled action that sends an email to the PM/stakeholder every 2 weeks on a particular day with a list of all items planned for the next sprint as a reminder to review the items before the sprint launches.