Use Cases for Post-Functions (Legacy)

Note: the Use Cases detailed on this page are still mostly valid! However, they are in the process of being updated, both in format and in specific post-function configurations that have been changed in recent JMWE updates.

This section has use cases that help you in understanding the usage of post functions. A few post-functions of JMWE have been deprecated and will no longer be enhanced. However, they still continue to work and you can configure and use the post-functions. But it is recommended to use their replacements instead.

On this Page

Assign to role member

A workflow post-function that assigns the target issue to a member of a selected project role. 

Sample use cases:

 On the creation of a Bug assign it to a user only if he is a Product Owner

  • Create a Product Owner project role, with the product owner as the only member.

  • Add the Assign to role member post-function to the Create transition of the Bug workflow.

  • Select Product Owner as the project role.

  • Select the Conditional execution check box Run this post-function only if a condition is verified.

  • Input the following code template in Condition.

    {{ issue.fields.issuetype.name == "Bug" }}

 Assign an issue to a member of the QA team when the issue is transitioned to Ready for testing status

  • Create a QA project role, with the testers as its members.

  • Add the Assign to role member post-function to the transition that leads to Ready for testing.

  • Select QA as the project role to look for.


 Assign an issue to a member of the Support - UTC project role only when the reporter time zone is UTC.

  • Add the Assign to role member post-function to the Create transition of the issue workflow.

  • Select Support-UTC as the project role.

  • Select the Conditional execution check box Run this post-function only if a condition is verified.

  • Input the following code in Condition.

    {{ issue.fields.reporter | userProperty("TimeZone") == "UTC" }}

On approving a Story assign the subtasks of the Story to a member of the Developer project role

  • Add the Assign to role member post-function to the Approve transition of the issue workflow.

  • Select the “Target Issue(s)” as “Sub-tasks of the current issue”

  • Select Developers as the project role.

Assign to last role member

A workflow post-function that assigns the target issue to the last assignee who belongs to the selected project role.

Sample use cases: 

 When a tester reopens an issue assign the issue to a Developer who last worked on it.

  • Create a Developer project role, with the developers as its members.

  • Add the Assign to last role member post-function to the Reopen transition.

  • Select Developer as the project role to look for.

 After testers have validated an issue, it should be assigned to the last product owner who worked on it for the functional validation. The product owner might either have been explicitly assigned to the issue before, to write the functional specification or have written the specification while creating the issue.

Assign the Story to the tester who last worked on the Story when all the bugs blocking the Story are fixed

Build-your-own (scripted) Post-function

A post-function that allows you to run an arbitrary Nunjucks template (script). This can be used to create your own post-functions.

Add a worklog entry to the issue. You can do this using the callJira custom Nunjucks filter.

Clear fields

A workflow post-function that clears the value(s) of the selected field(s) of the target issue.

 Clear the Fix Version/s field on the reopening of a ticket.

Clear a set of fields on all the linked issues of the current issue when an Abort is triggered on the current issue

Clear fields of linked issues - Deprecated - Use Clear Fields instead

A workflow post-function that clears the value of the selected field(s) of the issues linked to the current issue through a specific link type.

 Clear a set of fields on all the linked issues of the current issue when an Abort is triggered on the current issue

Comment issue(s)

A workflow post-function that creates a comment on the target issue(s). The text of the comment to be created can be any simple text or a text with Nunjucks annotations.

Sample use cases:

 A customer using Jira Service Desk should be notified via comment when someone has started working on their support request.

 On resolving or closing the issue, comment the issue with a summary of the worklog.

An issue is blocking another and you want to ensure the Assignee of the blocked issue is notified when the impediment has been resolved.

 Add a comment on all the sub-tasks when the parent is canceled

 On the Approval of an issue, copy the comment added if any to its sub-tasks.

 Add a comment on the Epic when its user story is resolved.

 The Service Desk Agent responsible for a support request should be notified when the linked Bug is resolved.

Comment linked issues - Deprecated - Use Comment issue(s) instead

A workflow post-function that creates a comment on all issues linked to the current issue through a selected link type. The text of the comment to be created can be any simple text or a text with Nunjucks annotations.

Sample use cases:

 An issue is blocking another and you want to ensure the Assignee of the blocked issue is notified when the impediment has been resolved.

 Add a comment on all the sub-tasks when the parent is canceled

 On the Approval of an issue, copy the comment added if any to its sub-tasks.

 Add a comment on the Epic when its user stories are resolved.

 The Service Desk Agent responsible for a support request should be notified when the linked Bug is resolved.

Copy comments to related issues

A workflow post-function that copies the comment(s) of the current issue to the specified related issues

Sample use cases:

 When a developer transitions an issue to "Customer Feedback" copy the developer's comment on the transition screen to the linked issue.

 Configure bi-directional sync of comments between the issues linked through the “causes” link type.

Create issue

A workflow post-function that creates one or more new issue(s). The specifications of the issue(s) to be created can be customized using the options provided.

Sample use cases:

 Create a documentation ticket only if "Needed" is selected in the "Documentation ticket" checkboxes field

 On the approval of a Story, create two sub-tasks: one for Development and another for QA.

 We use Jira Service Desk for support and Jira Software for development. When the support agent's problem analysis identifies a bug, a Bug should be created in the development project.

 To onboard a new employee in the HR database, create tasks for the New Employee ticket for Configuring a new computer system, Set up an employee phone and Configure a new employee work space.

 An Epic has a Story and the Story has a sub-task. When the sub-task is reopened we want to create a bug in another project linking it to the sub-task. On creation of the Bug, set its Epic link to the Story's Epic link

 When a user raises a bug report, post-verification, automatically add it to the backlog in the development project and copy the issue links of the Bug to the newly created issue.

Copy field value from linked issues

A workflow post-function that sets the value(s) of a selected field to the value(s) from the same/different field of an issue linked to the current issue through a selected link type.

Sample use cases:

 Copy the Fix Version/s field from the Epic to a Story, while creating a Story.

 Automatically add the Reporter of an Epic to the watchers of its User Stories while creating a Story.

Copy field value to linked issues

A workflow post-function that copies the value(s) of a selected field into the same/different field of all issues linked to the current issue through a selected link type.

Sample use cases:

 Copy the Fix Version/s field from the Stories to Epic, after resolving a user story.

 On resolving an issue, copy the Fix Versions to all the linked issues regardless of the link type.