Use cases for post functions (Legacy)

Note: this page includes legacy Use Cases for JMWE for Jira Data Center/Server. These use cases are in the process of being verified and updated; you can still use them, but you may encounter discrepancies between what is documented and what you see in JMWE.

This section has use cases which help you in understand the usage of Post-functions provided by JMWE.

Assign to role member

This post function can be used to assign an issue to the 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

Add the Assign to role member to the Create transition.
Select Product Owner as the Project Role
Select Use selected assignee, only if a member of the required role option

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 status.
Select QA as the project role to look for.

Click here to know the post-function features

Assign to last role member

This post function can be used assign an issue to the last role member of a selected project role. This is very much similar to the Assign to role member, except that it always looks for the last role member.

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 to the Reopen transition.
Select Developer as the Project Role

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.

Create a Product Owner project role, with the product owners as its members.
Add the Assign to last role member post-function to the Validate transition of the workflow.
Select Product Owner as the project role to look for.
Select Include Reporter option in case a product owner created the issue but was never assigned to it afterward.

Click here to know the post-function features

Clear field value

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

Add the Clear field value post-function to the Reopen transition of the workflow.
Select the field Fix Version/s to from Field.

Clear field of related issues

This post-function clears the value of the selected field(s) of the issue's related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.)

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

This post-function can be used to comment an issue either by using a Raw value or the result of a Groovy expression or a Groovy template.

Sample use cases:

A customer using Jira Service Desk should be notified via a 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.

Click here to know the post-function features

Comment related issues

This post-function creates a comment on all issue's related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.). The text of the comment can be either a text, optionally including a Groovy template markup, or the result of the evaluation of a Groovy expression.

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 cancelled

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

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

Click here to know the post-function features

Create/Clone issue

This post-function can be used to create a new issue.

Sample use cases:

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

Create a bug in Project B when the developer confirms a Bug in Project A for the component UI

To onboard a new employee in the HR database, create tasks one for each value selected in "Onboarding Tasks" multi-valued field

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

Click here to know the post-function features

Copy field value from related issues

This post-function sets the value of a field to the value of a field in related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.)

Sample use cases:

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

Click here to know the post-function features

Copy field value to related issues

This post-function copies the value of a field to all related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.)

Sample uses cases:

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

Click here to know the post-function features

Copy field value from parent issue

This post-function can be used to set the value(s) of a selected field with value(s) from the same field of an issue's parent issue.

Sample use cases:

When creating a child bug of another bug (i.e. the parent bug), copy the fields Assignee, Component/s and Affects Version/s if they are left empty.

Click here to know the post-function features

Copy field value to parent issue

This post-function can be used to copy the value(s) of a selected field to the same field of the issue's parent issue.

Sample use cases:

Copy the labels from each sub-task to its parent when the sub-task is closed.

Click here to know the post-function features

Copy value from field to field

This post-function can be used to copy the value(s) of one field to another field of the same issue.

Sample use cases:

Set the component of an issue with a value selected from a cascading field that carries the Main and Sub-components in parent and child.

Issues in our project are fixed in the version they are found. So I want to copy the Affects Version/s of the issue to the Fix Versions, on resolving the issue.

I want 'Capture for JIRA Environment' field to be copied to the 'Environment' field when a bug is created using Capture for JIRA.

Copy value from a Single Version Picker select list to the Fix Version(s) field if the resolution provided while closing the issue is "Fixed".

Click here to know the post-function features

Email issue

This post-function is used to send an email to certain recipients specified in the post-function configuration

Sample use cases:

Send an Email to the voters of the issue when a new feature is approved.

On the creation of an issue send an Email notification to email addresses in a checkboxes custom field type.

Click here to know the post-function features

Increase value of field

This post-function is used to increase the value of a numerical field by one.

Sample use cases:

Track the number of times a bug fix was rejected by the QA team.

Click here to know the post-function features

Link issues to the current issue

This post-function is used to link the current issue to all issues that satisfy a parameterized JQL query.

Sample use cases:

Link all the Faults in Service desk project to the current issue with "blocks" link type

Click here to know the post-function features

Scripted (Groovy) operation on issue

This post-function is used to execute a Groovy expression against the current issue.

Sample use cases:

Copy attachments of the sub-tasks to the parent

Copy the attachments of the issue to the newly created issue

Click here to know the post-function features

Set Field Value From User Property value

This post-function is used to set a field to the value of a user property of the current user or the user in an issue field.

Sample use cases:

Store the Country, Department, Location, and Pin information of the Reporter of an issue into the issue itself while creating it.

Click here to know the post-function features

Set field value of related issues

This post-function is used to set a selected field of all issues related to the current issue through a selected link type.

Sample use cases:

Display the Man hours (a custom Numeric field) of an Epic as the sum of Man hours of all the user stories linked to the Epic.

Set the issue's due date to the maximum due date set in its sub-tasks.

On the Approval of an issue copy its components to issues linked to it with duplicates link type, only if the linked issue belongs to the same project as the current issue.

On the creation of a sub-task add its summary to the description of its parent

Click here to know the post-function feature

Set field value

This post function is used to set a field value with value(s) specified in the post-function. The value set can either be a fixed text or the result of the evaluation of a Groovy expression or the result of a Groovy template.

Sample use cases:

Set a custom field with the total work log entered during the rework on an issue

Assign a reopened issue to the last person who last commented it.

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

Capture the developer who resolved an issue in a custom single-user picker field

Assign the issue to the Project lead if the issue is unassigned

On creating an issue, pick the component of the issue from a cascading field that carries the Main and Sub-components

Set the Component/s of the issue to components whose lead is the current user

On creating a Bug set its Affects Version/s to the most recently released version

On creating a Bug with Highest priority set its Fix Version/s to the upcoming release

Set the Affects Version/s of the issue to Affects Version/s of all its linked issues

Set the due date to today's date

Identify all comments made between transitions A and B and add them to a custom text field

Set the due date to issue created plus five days

Select the Installation tasks in the Checkboxes/Multi-select type field when all the Installations are done

On the creation of an issue set a custom text field called Current time to the current time in the current user's timezone

Add the members of the selected Organizations to the Watchers of the issue

Add the issue to the current active Sprint

Set the Assignee of the issue based on the selected office

Click here to know the post-function features.

Set issue, user or project entity property value post-function

This post-function is used to set the issue, user or project entity property.

Sample use cases:

On the creation of a ticket, create a user entity property Profession for the current user.

Click here to know the post-function features.

Set issue security level based on user's project role

This post-function is used to set the Security Level of the current issue based on the project role to which the current user belongs.

Sample use cases:

Set a different issue security level depending on whether the issue is being created by an internal user or by an external user (e.g. a customer).

Click here to know the post-function features

Transition issue

This post-function is used to trigger a transition on the current issue

Sample use cases:

Start the progress on an issue immediately after its creation if its priority is Highest.

Transition an issue only when all the Business Approvers approve the request through a comment "Approved"

Click here to know the post-function features

Transition related issues

This post-function triggers a transition on all issues related to the current issue

Sample use cases:

Resolve the associated support request(s) when a bug is resolved, and copy all comments from the bug to the support request(s)

Click here to know the post-function features

Transition parent issue

This post-function is used to trigger a transition on the parent issue of the current issue

Sample use cases:

Start progress on the parent issue when someone started working on its sub-task.

Click here to know the post-function features

Unlink issues from the current issue

This post-function is used to unlink issues from the current issue based on the result of a Groovy condition.

Sample use cases:

On rejection of an issue, unlink all its linked issues

Click here to know the post-function features

You are viewing the documentation for Jira Data Center/Server.