View Source

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

On this page:

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

Add the Clear field value of related issue post-function to the Abort transition of the workflow.
Select Issues linked to the current issue through any link type from Which Issue(s)
Select all the fields to be emptied from Field.

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.

Add the Comment issue post-function to the Start Progress transition.
Select the Comment type as Groovy template

Write the following content in the Comment section:

We have started working on your support request - $issue.key. We will get back to you within 24 hours.

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

Add the Comment issue post-function to the Start Progress transition.
Select the Comment type as Groovy template

Write the following content in the Comment section:

<% def count = 1 
issue.get("worklog").each(){
  print "Worklog "+ count + "\n" + " Started :" + it.getStartDate() + "\n" + " Time Spent :" + it.getTimeSpent() + "\n" + " Work Description :" + it.getComment() + "\n"
  count = count + 1
}%>

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 the Comment related issues post-function to the transition that resolves the current issue.
Select Issues linked to the current issue through the following link type under Which Issue(s)
Choose the issue link type blocks
Select the Comment type as Groovy template

Write the following content in the Comment section.

The impediment $issue.key- $issue.summary has been resolved.

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

Add the Comment related issues post-function to the Cancel transition
Select the Comment type as Groovy template
Select Sub-tasks of the current issue under Which issue(s)

Write the following content in the Comment section.

The parent of the issue i.e $issue.key has been canceled.

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

Add the Comment related issues post-function to the Approve transition
Select the Comment type as Groovy template
Select Sub-tasks of the current issue under Which issue(s)

Write the following content in the Comment section.

if(transientVars.comment)
  return transientVars.comment
else
  return ""

Move this post-function after the "Add a comment to an issue if one is entered during a transition" post-function.

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

Add the Comment related issues post-function to the Resolved transition of the Bug workflow.
Select the Comment type as Groovy template
Select Issues linked to the current issue through the following link type under Which Issue(s)
Choose the issue link type blocks

Write the following content in the Comment section.

$issue.key has been resolved. You should get back to the customer.

Check the Restrict to internal (Jira Service Desk only) option to make sure the customer doesn't see the comment.

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.

Add the Create/Clone issue post-function to the transition Approve of the Story workflow to create a QA ticket.
Select Same as current issue from the Project field.
Select Subtask from the Issue type field.
Select Current issue from the Parent issue field.
Add a Summary
Task for <%=it%>
Select the option under "Multiple issue creation"
Input the following value:
["Development","QA"]

Two sub-tasks will be created, one for "Development" and another for "Subtask"

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

Add the Create/Clone issue post-function to the Start Progress transition of the Bug workflow.
Select the Production project from the Project field.
Select Bug from the Issue type field.
Set Summary field to $issue.summary
Set Linked Issues field to be copied from the current issue
Select is cloned by in the Link to new issue section.
Select the Conditional execution section and write the following script:
issue.get("components").any{it.name == "UI"}

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

Add the Create issue post-function to the transition Create of the New Employee ticket workflow.
Select Same as current issue from the Project field.
Select Task from the Issue type field.
Select the link type from the main issue to the new issues under "Link type"
Edit the Summary field value to:
Task for <%=it.value%>
Select the option under "Multiple issue creation"
Input the following value:
issue.get("Onboarding Tasks")

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

Add the Create issue post-function to the Reopen transition of the sub-task workflow.
Select the project from Project
Select the Bug in Issue type
Select is caused by in Link to new issue
Select the Epic Link field in Set fields of new issue.
Select the Value type as Groovy expression

Write the following in the Value section

if(issue.getLinkedIssues('is caused by'))
{
  issue.getLinkedIssues('is caused by').first().getParentObject().get("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.

Add the Copy field value from related issues post-function to the Create transition of the Story workflow.
Select Fix Version/s in Source Field.
Select Same as the source field in Destination Field.
Choose Issues that belong to the current Epic from Which Issue(s)

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.

Add the Copy field value to related issues post-function to the Resolve transition of the Story workflow
Select Fix Version/s in Source Field.
Select Same as the source field in Destination Field.
Choose Epic of the current issue from Which issue(s).
Check Add source value(s) to destination field option.

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.

Add the Copy field value from parent issue post-function to the Create transition of the sub-task workflow.
Select Assignee in Field.
Select Copy only if not set option.
Repeat the above steps for the Component/s and Affects Version/s fields.

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.
Add the Copy field value to parent issue post-function to the Close transition of the Sub-task workflow.
Select Labels in Field.
Select the Add source value(s) to destination field option.

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.

Add the Copy value from field to field post-function to the Create transition of the issue workflow.
Select the Cascading field as the Source field.
Select the Components field as the Destination field.
Select Return "parent - child" for cascading custom fields option.

Note: The Component name should be in Component - Subcomponent format.

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.

Add the Copy value from field to field post-function to the Resolve transition of the issue's workflow.
Select Affects Version/s as the Source field.
Select Fix Version/s as the Destination field.

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

Add the Copy value from field to field post-function to the Create transition of the Bug workflow.
Select Capture for JIRA Environment as the Source field.
Select Environment as the Destination field.

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".

Add the Copy value from field to field post-function to the Close transition of the issue's workflow.
Select the Single version picker in the Source field.
Select the Fix Version/s in the Destination field.
Select the Conditional execution and write the following script:
issue.get("resolution")?.getName() == "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.
Add the Email issue post-function to the Approve transition of the issue's workflow.
Input the subject of the Email in Subject
Select the Voters in Issue members under Recipients.

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

Add the Email issue post-function to the Create transition of the issue's workflow.
Input the subject of the Email in Subject
Write the following Groovy template in Email addresses field.
${issue.getAsString("EmailIds")}

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.
Create a Rejection counter numerical custom field.
Add the Increase value of field post-function to the Reject transition of the Bug workflow.
Select the Rejection counter field.

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

Add the Link issues to current issue post-function to the transition

Input the following JQL expression

project = "Service Desk project" and issuetype =  Fault

Select 50 in Max. issues
Select the blocks link type in Issue link

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

Add the Scripted (Groovy) operation on issue post-function to the transition

Input the following Groovy expression

import com.atlassian.jira.issue.AttachmentManager
AttachmentManager attachmentManager = ComponentAccessor.getAttachmentManager()

def attach = []
issue.get("subtasks").each{
  if(it.get("attachment"))
  {
    attach += it.get("attachment") 
  }
}
attach.each{
  attachmentManager.copyAttachment(it,currentUser,issue.key)
}

Note that testing the script would copy the attachments to the issue

Copy the attachments of the issue to the newly created issue

Add the Scripted (Groovy) operation on issue post-function to the Create transition

Input the following Groovy expression

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.AttachmentManager

AttachmentManager attachmentManager = ComponentAccessor.getAttachmentManager()
def attach = issue.get("attachment")

attach.each{
  attachmentManager.copyAttachment(it,currentUser,transientVars.newIssue?.key)
}

Note that testing the script would copy the attachments to the issue

Place the post-function to the end of the list of post-functions.

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.

Create a user entity property to store the Country information.
Add the Set field value of user property post-function to the transition
Select the field to which the Country information is supposed to be copied.
Repeat the above steps for all the other fields.

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.

Add the post-function Set field value of related issues to the Create transition of the Story workflow.
Select the Man hours field.
Choose Epic of the current issue under Which Issue(s)
Select the Value type as Groovy template

Write the following content in the Value section.

<%=textutils.noNull(issue.get("Man hours")) + textutils.noNull(linkedIssue?.get("Man hours"))%>

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

Add the Set field value of related issues to the Create transition of the subtask's workflow.
Select the Due date field.
Choose Parent issue of the current issue under Which issue(s)
Select the Value type as Groovy Expression
Write the following content in the Value section.
issue.get("duedate")
Write the following in Conditional execution section
linkedIssue?.get("duedate") <= issue.get("duedate")

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.

Add the Set field value of related issues post-function to the Approval transition of the issue's workflow.
Select the Components field.
Select Issues linked to the current issue through the following link type under Which issues
Choose the issue link type as duplicates
Select the Value type as Groovy Expression
Write the following content in the Value section.
issue.getAsString("components")

Write the following in Conditional execution section

issue.get("project").getKey() == relatedIssue?.get("project")?.getKey()

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

Add the Set field value of related issues post-function to the Create transition.
Select the Description field.
Select Parent issue of the current issue under Which issue(s)
Select Groovy expression in the Value type.

Write the following content in the Value section.

org.codehaus.groovy.runtime.NullObject.metaClass.toString = {return ''}
relatedIssue?.get("description").toString() + "\n" + issue.get("summary")

Place the post-function after the Creates issue originally built-in post-function.

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

Add the Set field value post-function to the Rework transition of the issue's workflow.
Select the Time spent on rework custom field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

return issue.getModifiedFields().get("worklog")?.newValue?.worklogResult()?.getWorklog()?.getTimeSpent()

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

Add the Set field value post-function to the Reopen transition of the issue's workflow.
Select the Assignee field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

if(issue.get("comment"))
{
  issue.get("comment").last().getAuthorApplicationUser()
}

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

Add the Set field value post-function to the Create transition.
Select the Watchers field.
Select Groovy expression in the Value type.
Write the following content in the Value section.
issue.epic?.get("reporter")
Select Add source value(s) to destination field option
Place the post-function after the Creates issue originally built-in post-function.

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

Create a Resolved By single-user picker custom field.
Add the Set field value post-function to the "Resolve Issue" transition.
Select the Resolved By field.
Select Groovy expression in the Value type.
Write the following content in the Value section.
currentUser.name

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

Add the Set field value post-function to the Create transition of the issue workflow.
Select the Assignee field.
Select Groovy expression in the Value type.
Write the following content in the Value section.
issue.get("project").getProjectLead()
Write the following content in the Conditional execution section.
issue.get("assignee")
Place the post-function after the Creates issue originally built-in post-function.

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

Add the Set field value post-function to the Create transition of the issue's workflow.
Select the Component/s field.
Select Groovy expression in the Value type.

Write the following content in it.

import com.atlassian.jira.issue.fields.CustomField;
CustomField customField = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Cascade");
def value = issueObject.getCustomFieldValue(customField);
return (value?.get(null)?.getValue() + "-" + value?.get("1"))

Place the post-function after the Creates issue originally built-in post-function.

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

Add the Set field value post-function to the Create transition of the issue workflow.
Select the Components field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

def components = issue.getAvailableOptions("components")
def newComponents = components.findAll{
  it?.getLead() == currentUser.getKey()
}
return newComponents

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

Add the Set field value post-function to the Create transition of the Bug's workflow.
Select the Affects Version/s field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

def versions = issue.getAvailableOptions("versions")
def versionMap = [:]
if (versions)
{
  versions.each(){
    if(it.getReleaseDate())
    {
      versionMap.put(it?.getReleaseDate(),it.getName())
    }
  }
}
if(versionMap.min{it.key}?.getValue())
{
  return versionMap.min{it.key}?.getValue()
}
else
{
  return versions = []
}

Place the post-function after Creates issues originally built-in post-function.

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

Add the Set field value post-function to the Create transition of the Bug's workflow.
Select the Affects Version/s field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

def versions = issue.getAvailableOptions("versions")
def versionMap = [:]
if (versions)
{
  versions.each(){
    if(it.getReleaseDate())
    {
      versionMap.put(it?.getReleaseDate(),it.getName())
    }
  }
}
if(versionMap.min{it.key}?.getValue())
{
  return versionMap.min{it.key}?.getValue()
}
else
{
  return versions = []
}

Write the following in Conditional execution section
issue.get("priority").getName() == "Highest"
Place the post-function after Creates issues originally built-in post-function.

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

Add the Set field value post-function to the transition
Select the Affects Version/s field.
Select Groovy expression in the Value type.

Write the following content in the Value section

Set versions = []
issue.get("issuelinks").each(){
  versions += it.getDestinationObject().get("versions")
}
return versions

Set the due date to today's date
Add the Set field value post-function to the transition.
Select the Due date field.
Select Groovy expression in the Value type.
Write the following content in the Value section.
new Date()

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

Create Date-Time picker fields Date of Transition A and Date of Transition B
Create a Mulit-line text field Comments between transitions A and B
Add the Set field value post-function to the transition A
Select the Date of Transition A field.
Select Groovy expression in the Value type.
Write the following in the Value section
new Date()
Add the Set field value post-function to the transition B.
Select the Date of Transition B field.
Select Groovy expression in the Value type.
Write the following in the Value section
new Date()
Add the Set field value post-function to the transition on whose trigger you want to identify the comments
Select the Comments between transitions A and B field

Write the following in the Value section

Comments between Transition A and Transition B are:
<% issue.get("comment").each() {
  if(it.created > issue.get("Date of Transition A") && it.created < issue.get("Date of Transition B") || it.updated > issue.get("Date of Transition A") && it.updated < issue.get("Date of Transition B"))
  {
   print "Comment added/updated by: "+ it.getAuthorFullName() + " at " + it.getUpdated() + "\n" + it.body + "\n"
  }
}
%>

Set the due date to issue created plus five days
Add the Set field value post-function to the transition.
Select the Due date field.
Select Groovy expression in the Value type.
Write the following content in the Value section.
issue.get("created") + 5

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

Add the Set field value post-function to the transition.
Select the Checkboxes field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

issue.getAvailableOptions("<Name of the field>").findAll{
  it.getValue().contains("Installation")
}

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 Set field value post-function to the Create transition of the issue's workflow.
Select the Current time field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

import com.atlassian.jira.timezone.TimeZoneManager

// access timeZone of current user

def userTimeZone = getComponent(TimeZoneManager).getLoggedInUserTimeZone()
c1 = GregorianCalendar.getInstance(userTimeZone);
return c1.format("HH:mm")

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

Add the Set field value post-function to the transition of the issue's workflow.
Select the Watchers field.
Select Groovy expression in the Value type.

Write the following content in the Value section.

import com.atlassian.servicedesk.api.organization.OrganizationService
import com.atlassian.servicedesk.api.util.paging.SimplePagedRequest

def orgs = issue.get("Organizations");
if (!orgs)
    return [];
def organizationService = getComponent(OrganizationService)
def pagedRequest = SimplePagedRequest.paged(0,1000)
Set users = []

for (org in orgs) {
    def query = organizationService.newUsersInOrganizationQuery().customerOrganization(org).pagedRequest(pagedRequest).build()
    result = organizationService.getUsersInOrganization(currentUser, query)
    if (result.isRight())
      users.addAll(result.getRight().getResults())  
}
return users;

Add the issue to the current active Sprint

Add the Set field value post-function to the transition of the issue's workflow.
Select the Sprint field.
Select Groovy expression in the Value type.

Write the following content in the Value section and replace the <Board Id> with the actual board id in the code.

import com.atlassian.greenhopper.service.rapid.view.RapidViewService
import com.atlassian.greenhopper.service.sprint.SprintService
import com.atlassian.greenhopper.service.PageRequests
import com.atlassian.greenhopper.service.sprint.SprintQuery
import com.atlassian.greenhopper.service.sprint.Sprint
import com.atlassian.greenhopper.service.sprint.Sprint.State
 
def boardId = <Board Id>
def board = getComponent(RapidViewService).getRapidView(currentUser, boardId).get()
def SprintService = getComponent(SprintService)

def sprintQuery = SprintQuery.builder().states(Collections.singleton(State.ACTIVE)).build()
def sprintsOutcome = SprintService.getSprints(currentUser, board, PageRequests.all(), sprintQuery)
 
if (sprintsOutcome.isInvalid()){
  throw new UnsupportedOperationException(sprintsOutcome.toString())
}
def sprints = sprintsOutcome.get().getValues()
 
if (sprints.size() > 1){
  throw new UnsupportedOperationException("More than one sprint is active")
}
return sprints[0].getId()

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.

Add the Set issue, user or project entity property value post-function to the Create transition of the issue workflow.
Select Current user from Entity field.
Input Profession in Property name field.
Select Constant or Groovy Template in Value type field.
Input "Doctor" in the Value field.
Place the post-function after the Creates issue originally built-in post-function.

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).

Add the Set issue security from user property function post-function to the Create transition of the issue workflow.
Select the Security Level field.
Select Administrators in the Project Role.
Select Admin Prod in the Issue Security Level
Place the post-function after the Creates issue originally built-in post-function.

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.

Add the Transition issue post-function to the Create transition of the issue workflow.
Input the transition name or ID of Start Progress transition
Place the post-function after the Creates issue originally built-in post-function.
Write the following script in Conditional execution
issue.get("priority").getName() == "Highest"

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

Add the Transition issue post-function to the transition of the issue workflow.
Input the transition name or ID of the transition you wish to trigger

Write the following script in Conditional execution

def HashSet users = []
def regExp = ~/^(?i)approved.*/
issue.get("comment").each{
  if(it.getBody().matches(regExp) &&
    it.getAuthorApplicationUser() in issue.get("MUP") &&
    !(it.getAuthorApplicationUser() in users))
  {
    users += it.getAuthorApplicationUser()
  }
}
users.size()==issue.get("MUP")?.size()

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)

Add the Transition related issues post-function to the transition Resolve of the Bug workflow.
Input the transition name or ID of the Resolve transition of the support workflow.
Select Issues linked to the current issue through any link type from Which Issues
Set the Comment field to copy the comments from the current issue.
Place this post-function at the end in the list of post-functions.

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.

Add the Transition parent issue post-function to the Start Progress transition of the workflow.
Input the Start progress transition name/ID.
Place this post-function at the end in the list of post-functions.

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
Add the Unlink issues from the current issue post-function to the Reject transition of the workflow.
Write true in Condition

Click here to know the post-function features

Assign to role member

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

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

Assign to last role member

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

Clear field value

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

Clear field of related issues

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

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.

Comment related issues

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.

Create/Clone issue

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

Copy field value from related issues

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

Copy field value to related issues

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

Copy field value from parent issue

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.

Copy field value to parent issue

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

Copy value from field to field

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".

Email issue

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.

Increase value of field

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

Link issues to the current issue

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

Scripted (Groovy) operation on issue

Copy attachments of the sub-tasks to the parent

Set Field Value From User Property value

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

Set field value of related issues

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

Set field value

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 issue, user or project entity property value post-function

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

Set issue security level based on user's project role

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).

Transition issue

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"

Transition related issues

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

Transition parent issue

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