---
title: "Use Cases for Post-Functions (Legacy)"
canonical: "https://support.appfire.com/space/JMWEC/465373017/Use%20Cases%20for%20Post-Functions%20(Legacy)"
format: markdown
---
> Macro (aura-html)

> 📝 **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.

## [Assign to role member](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=jmwec&title=Assign%20to%20role%20member&linkCreation=true&fromPageId=465373017)

<span style="color: #091e42">A workflow post-function that assigns the target issue to a member of a selected project role. </span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> On the creation of a Bug assign it to a user only if he is a Product Owner</span>

<details>
<summary>Steps</summary>

- 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`.
</details>

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

<details>
<summary>Steps</summary>

- 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.
</details>

####   
:light_bulb_on:<span style="color: #000000"> Assign an issue to a member of the Support - UTC project role only when the reporter time zone is UTC.</span>

<details>
<summary>Steps</summary>

- 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`.
</details>

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

<details>
<summary>Steps</summary>

- 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.
</details>

## [Assign to last role member](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466225934)

<span style="color: #091e42">A workflow post-function that assigns the target issue to the last assignee who belongs to the selected project role.</span>

**Sample use cases:** 

#### :light_bulb_on:** W**<span style="color: #172b4d">hen a tester reopens an issue assign the issue to a Developer who last worked on it.</span>

<details>
<summary>Steps</summary>

- 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.
</details>

#### :light_bulb_on: 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.

<details>
<summary>Steps</summary>

- 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 User Story 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
</details>

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

<details>
<summary>Steps</summary>

- Add the *Assign to last role member *post-function to the **Done **transition of the Bug workflow
- Select “Target issue(s)” as “Issues linked to the current issue through the following link type”
- Select “blocks”
- Select `Testers`as the project role to look for.
- Select the “Conditional execution” option
- Input the following script:
</details>

## [Build-your-own (scripted) Post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466289991) 

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

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

<details>
<summary>Steps</summary>

1. Add the “Build-your-own (scripted)” post-function to the transition
2. Input the following Nunjucks template
  
3. Save the post-function and publish the workflow
</details>

## [Clear fields](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466226128)

<span style="color: #091e42">A workflow post-function that clears the value(s) of the selected field(s) of the target issue.</span>

#### :light_bulb_on:<span style="color: #172b4d"> Clear the Fix Version/s field on the reopening of a ticket.</span>

<details>
<summary>Steps</summary>

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

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

<details>
<summary>Steps</summary>

- Add the *Clear field value *post-function to the **Abort **transition of the workflow.
- Select the “Target Issue(s)” as “Issues linked to the current issue through any link type”
- Select all the fields to be emptied from `Field`
</details>

## [Clear fields of linked issues](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466289629) - Deprecated - Use [Clear Fields](/wiki/spaces/MWECS/pages/78481302) 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.

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

<details>
<summary>Steps</summary>

- Add the *Clear field value of linked issues *post-function to the **Abort **transition of the workflow.
- Select all the fields to be emptied from `Field`
</details>

## [Comment issue(s)](#)

<span style="color: #091e42">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.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> A customer using Jira Service Desk should be notified via comment when someone has started working on their support request.</span>

<details>
<summary>Steps</summary>

- Add the *Comment issue(s) *post-function to the **Start Progress **transition of the issue's workflow.
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment issue(s) *post-function to the **Resolve **transition of the issue's workflow.
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment issue(s)* post-function to the transition that resolves the current issue.
- Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”
- Select the issue link type `blocks` under “Issue Link”
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment issue(s)*  post-function to all the transitions of the internal issue workflow.
- Select the “Target issue(s)” as “Sub-tasks of the current issue”
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment issue(s)* post-function to all the transitions of the internal issue workflow.
- Select the “Target issue(s)” as “Sub-tasks of the current issue”
- Write the following content in the `Comment` section.
</details>

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


<details>
<summary>Steps</summary>

- Add the *Comment issue(s)* post-function to the **Resolved** transition of the Story workflow.
- Select the “Target issue(s)” as “Epic of the current issue”
- Write the following content in the `Comment` section.
</details>

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


<details>
<summary>Steps</summary>

- Add the *Comment issue(s) *post-function to the **Resolved **transition of the Bug workflow.
- Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”
- Select the issue link type `blocks` under “Issue Link”
- Write the following content in the `Comment` section.
- Check the `Restrict to internal (Jira Service Desk only)` option to make sure the customer doesn't see the comment.
</details>

## [Comment linked issues](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465373854) - 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:**

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

<details>
<summary>Steps</summary>

- Add the *Comment linked issues* post-function to the transition that resolves the current issue.
- Choose the issue link type `blocks`
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment linked issues*  post-function to all the transitions of the internal issue workflow.
- Choose the issue link type is Parent of
- Write the following content in the `Comment` section.
</details>

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

<details>
<summary>Steps</summary>

- Add the *Comment linked issues* post-function to all the transitions of the internal issue workflow.
- Choose the issue link type `is Parent of`
- Write the following content in the `Comment` section.
</details>

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


<details>
<summary>Steps</summary>

- Add the *Comment linked issues* post-function to the **Resolved** transition of the Story workflow.
- Choose the issue link type `belongs to Epic`
- Write the following content in the `Comment` section.
</details>

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


<details>
<summary>Steps</summary>

- Add the *Comment linked issues *post-function to the **Resolved **transition of the Bug workflow.
- Choose the issue link type `blocks`
- Write the following content in the `Comment` section.
- Check the `Restrict to internal (Jira Service Desk only)` option to make sure the customer doesn't see the comment.
</details>

## [Copy comments to related issues](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465474211)

<span style="color: #091e42">A workflow post-function that copies the comment(s) of the current issue to the specified related issues</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> When a developer transitions an issue to "Customer Feedback" copy the developer's comment on the transition screen to the linked issue.</span>

<details>
<summary>Steps</summary>

- Add the *Copy comments to related issues* post-function to the transition.
- Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”
- Select the issue link type under “Issue Link”
- Choose `The comment added on the transition screen, if any` under `Comments to copy`
- Click on `Add`
</details>

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

<details>
<summary>Steps</summary>

- Create a global transition “Sync Comments”
  - Add the *Copy comments to related issues* post-function to the transition
  - Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”
  - Select “causes” under “Issue Link”
  - Choose `All comments`
  - Add another *Copy comments to related issues* post-function to the transition
  - Select the “Target issue(s)” as “Issues linked to the current issue through the following link type:”
  - Select “is caused by” under “Issue Link”
  - Choose `All comments`
  - Add a few seconds delay
- Click on `Add`

Now when you trigger the transition on the issue(s), the newly added comments on the issue are added to the linked issue
</details>

## [Create issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916)

<span style="color: #091e42">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.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Create a documentation ticket only if "Needed" is selected in the "Documentation ticket" checkboxes field</span>

<details>
<summary>Steps</summary>

- Add the *Create issue *post-function to the transition on whose trigger you want to create a documentation ticket
- Select `Documentation` from the `Project` field.
- Select `Document` from the `Issue type` field.
- Select `caused by` in the `Link to new issue` section.
- Add an appropriate Summary (such as `Release documentation`)
- Select the conditional execution and write the following template
</details>

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

<details>
<summary>Steps</summary>

- Add the *Create 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 an appropriate Summary (such as `Validation`)
- Repeat the above steps for the `Development `ticket.
</details>

#### :light_bulb_on: 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.

<details>
<summary>Steps</summary>

- Add the *Create issue *post-function to the **Create** transition of the Service desk project workflow.
- Select the `Development` project from the `Project` field.
- Select `Bug` from the `Issue type` field.
- Set Summary field to `{{issue.fields.summary}}`
- Select `caused by` in the `Link to new issue` section.
</details>

#### :light_bulb_on:<span style="color: #000000"> To </span>o<span style="color: #000000">nboard a new employee</span> <span style="color: #000000">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.</span>

<details>
<summary>Steps</summary>

- 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 `Sub-task` from the `Issue type` field.
- Select `Current issue` from the `Parent issue `field.
- Edit the `Summary` field value to : `Configuring a new computer system`
- Repeat the above steps for the remaining tickets.
</details>

#### :light_bulb_on:<span style="color: #000000"> 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</span>

<details>
<summary>Steps</summary>

- 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.
- Write the following in the `Value` section
</details>

#### :light_bulb_on:<span style="color: #172b4d"> 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.</span>

<details>
<summary>Steps</summary>

- Add the *Create issue *post-function to the transition the **Verify** of the Bug workflow.
- Select Development from the `Project` field.
- Select Task from the `Issue type` field.
- Select `duplicates` in the `Link to new issue` section.
- Add an appropriate Summary (such as `Duplicates - {{ issue.key}}`)
- Select the field `Linked Issues` from the `Set fields of new issue` section.
- Select `Copy value from current issue` from the drop-down.
- Add the post-function.
</details>

## [Copy field value from linked issues](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322381)

<span style="color: #091e42">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.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #000000"> Copy the </span><span style="color: #172b4d">Fix Version/s</span><span style="color: #000000"> field</span><span style="color: #172b4d"> </span><span style="color: #000000">from the Epic to a Story, while creating a Story</span><span style="color: #172b4d">.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value from linked issues *post-function to the **Create** transition of the Story workflow.
- Choose the `has Epic` link type.
- Select `Fix Version/s` in `Source Field`.
- Select `Same as source field` in the `Destination field`. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value from linked issues *post-function to the **Create** transition of the Story workflow.
- Select `Reporter` in the `Field`.
- Select `Watchers` in the `Destination field`.
- Choose the `belongs to Epic` link type.
- Select `Add value(s) to the issue` option. |
</details>

## [Copy field value to linked issues](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466257072)

<span style="color: #091e42">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.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #000000"> Copy the </span><span style="color: #172b4d">Fix Version/s</span><span style="color: #000000"> field</span><span style="color: #172b4d"> </span><span style="color: #000000">from the Stories to Epic, after resolving a user story.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value to linked issues *post-function to the **Resolve **transition of the Story workflow.
- Choose the `has Epic` link type.
- Select `Fix Version/s` in `Source Field`.
- Select `Same as source field` in the `Destination field`.
- Check `Add value(s) to the linked issue` option. |
</details>

#### :light_bulb_on:<span style="color: #000000"> On resolving an issue, copy the Fix Versions to all the linked issues regardless of the link type.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value to linked issues *post-function to the transition **Resolve.**
- Select `Fix Versions `in` Source Field.`
- Select `Same as source field` in the `Destination field`.
- Select `Any(except Issue/Subtask and Epic/Story)` in the `Issue Link Type` field.
- Select `Add value(s) to the linked issue` option. |
</details>

## [Copy field value from parent issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466257573)

<span style="color: #091e42">A workflow post-function that sets the value(s) of a selected field with value(s) from the same/different field of an issue's parent issue.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> When creating a child bug of another bug (i.e. the parent bug), copy the fields Assignee, Component and Affect versions if they are left empty. </span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value from parent issue *post-function to the **Create** transition of the sub-task workflow.
- Select `Assignee` in `Source Field`.
- Select `Same as source field` in the `Destination field`.
- Select `Copy only if not set` option.
- Repeat the above steps for the `Component/s` and `Affects` `Versions` fields. |
</details>

## [Copy field value to parent issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466257136)

<span style="color: #091e42">A workflow post-function that copies the value(s) of a selected field to the same/different field of the issue's parent issue.</span>

**Sample use cases :**

#### :light_bulb_on:<span style="color: #172b4d"> Copy the labels from each sub-task to its parent when the sub-task is closed.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy field value to linked issues* post-function to the **Create** transition of the Sub-task workflow.
- Select `Labels `in` Source Field`.
- Select `Same as source field` in the `Destination field`.
- Check the `Add subtask's value(s) to parent issue` option. |
</details>

## [Copy value from field to field](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466225614)

<span style="color: #091e42">A workflow post-function that copies the value(s) of a selected field to another field of the same issue. </span>

**Sample use cases :**

#### :light_bulb_on:<span style="color: #172b4d"> 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.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy value from field to field *post-function to the **Create** transition of the issue workflow.
- Select the `Cascading` field as the `From field`.
- Select the `Components` field as the `To field.`
- Select `Return "parent - child" for cascading custom fields` option.<br>Note: The Component name should be in `Component - Subcomponent` format. |
</details>

#### :light_bulb_on: Issues in our project are fixed in the version they are found . So I want to copy the Affect versions of the issue to the Fix Versions, on resolving the issue.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Copy value from field to field* post-function to the **Resolve** transition of the issue's workflow.
- Select `Affect Version/s` as the `From field.`
- Select `Fix Version/s` as the `To field`. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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 `From field.`
- Select `Environment` as the `To field.` |
</details>

#### :light_bulb_on: 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".

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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 `From field`.
- Select the Fix Version/s in the `To field`.
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Write the following content in `Condition.` |
</details>

## [Delete issue](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=jmwec&title=Delete%20issue%20%28Archived%29&linkCreation=true&fromPageId=465373017) 

<span style="color: #091e42">A workflow post-function that deletes one or more issues.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Automatically move the issue to a project when it is approved.</span>

<details>
<summary>Steps</summary>

Since there is no REST API to move issues between projects the workaround is to clone the issue into the desired project and delete the current issue.

|  |
| --- |
| **Clone issue**<br>- Add the *Create issue *post-function* *to the **Approve **transition of the issue's workflow.
- Fill in mandate/all fields of the new issue in "Set fields of new issue" section
- Save the post-function.<br>**Delete issue**<br>- Add the *Delete issue* post-function to the **Approve **transition of the issue's workflow.
- Add a delay of a few seconds to the post-function
- Save the post-function and publish the workflow |
</details>

#### :light_bulb_on: On rejecting a Story delete its subtasks 

<details>
<summary>Steps</summary>

***Not suggested***

|  |
| --- |
| - Add the *Delete issue* post-function to the **Reject **transition of the Story workflow.
- Select the “Target issue(s)” as “Sub-tasks of the current issue”
- Save the post-function and publish the workflow |
</details>

## [Display Message to user](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242070)

<span style="color: #091e42">A workflow post-function that </span><span style="color: #333333">displays a message on the issue view page to the user triggering the transition. </span>

#### :light_bulb_on:<span style="color: #172b4d"> On triggering a transition display a notification message on the issue view if a new issue has been created by the Create Issue(s) post-function with a link to the newly created issue.</span>

<details>
<summary>Steps</summary>

- Add the *Display Message to User post-function *to a transition.
- Input the "Message title" as `New issue created`
- Input the "Message body" as:
- Select the "Message type" as `Warning`
- Select the "Action link" option
- Input the "Action title" as `Go to the created issue`
- Select the "Navigate to URL" option
- Input the URL as

The message will be displayed as shown below in the issue view.

![JMWE for Jira Cloud project analysis interface showing workflow and issue management](media://65f552a0-dd5b-4b04-a0e9-c507e1904fdd)
</details>

## [Email issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322658)

<span style="color: #091e42">A post-function that will send an email to certain recipients of the target issues specified in the post-function configuration.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Send an Email to the voters of the issue when a new feature is approved.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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.` |
</details>

#### :light_bulb_on: Send an Email notification when an issue is created but avoid Email notification when the issue is cloned

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Email issue *post-function* *to the **Create **transition of the issue's workflow.
- Input the subject of the Email in `Subject`
- Select the `Recipients `you wish to send the Email to`.`
- Select Conditional execution and write the following script: |
</details>

#### :light_bulb_on: Send an Email notification to the reporter of the Service Desk ticket when a linked bug is created

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Email issue *post-function* *to the **Create **transition of the issue's workflow.
- Select the “Target issue(s)” as “Issues linked to the current issue through the following link type”
- Select “blocks” as the “Issue Link”
- Input the subject of the Email in `Subject`
- Select “Reporter” under “Issue members” |
</details>

## [Increase value of field](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466289696)

<span style="color: #091e42">A workflow post-function that increases the value of a selected numerical field by one.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Track the number of times a bug fix was rejected by the QA team.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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. |
</details>

## [Link issues to the current issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242225)

<span style="color: #091e42">A post-function that will link the current issue to all issues that satisfy a parameterized JQL query.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Link all the Faults in Service desk project to the current issue with "blocks" link type</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Link issues to current issue *post-function to the transition
- Input the following JQL expression
- Select `50` in Max. issues
- Select the `blocks` link type in `Issue link` |
</details>

## [Sequence of post-functions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322933)

<span style="color: #091e42">A post-function that runs a sequence of JMWE post-functions on the target issues. This is the easiest way of making sure that a series of post-functions run </span>*in a predictable order*<span style="color: #091e42"> during a transition - it is easier and more reliable than using </span>[Delayed execution](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322009)<span style="color: #091e42"> as was previously recommended.</span>

#### :light_bulb_on:<span style="color: #172b4d"> Cr</span><span style="color: #091e42">eate a new issue (using the Create Issue(s) post-function) and </span>*then*<span style="color: #091e42"> send a notification email mentioning the new issue.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the Sequence of post-functions post-function
  - Add the [Create issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466256916) post-function to create a subtask
  - Add the [Email issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466322658) post-function to send an email. Refer to the issue created by the previous post-function using this:
- Save the post-function |
</details>

#### :light_bulb_on:<span style="color: #172b4d"> To clone an issue and its subtasks to another project</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| 1. <span style="color: #172b4d">Add the "Sequence of post-functions" post-function to the transition</span>
2. <span style="color: #172b4d">In the sequence add the "Create issue" post-function.</span>
  1. <span style="color: #172b4d">Select the destination project in "Project"</span>
  2. <span style="color: #172b4d">Select the "Issue type" as "Calculated" and input</span>
  3. <span style="color: #172b4d">Select the "Link to new issue" as "clones"</span>
  4. <span style="color: #172b4d">Configure the fields</span>
  5. <span style="color: #172b4d">Click on Save</span>
3. <span style="color: #172b4d">Add another "Create issue" post-function to clone the sub-tasks</span>
  1. <span style="color: #172b4d">Select the destination project in "Project"</span>
  2. <span style="color: #172b4d">Select the "Issue type" as "Subtask"</span>
  3. <span style="color: #172b4d">Under the "Parent issue" input the following template:</span>
  4. Select "Multiple issue creation" option and input the following template:
  5. Save the post-function.
4. Click on "Save"
5. Publish the workflow. |
</details>

#### :light_bulb_on: Assign the subtasks of the current issue to the Developers project role and send an email to the assignee of the subtask

<details>
<summary>Steps</summary>

|  |
| --- |
| 1. Add the "Sequence of post-functions" post-function to the transition
  1. In the sequence add the Assign to role member post-function
  2. Select the project role “Developers”
  3. Save the post-function
  4. Add “Email issue” post-function
  5. Input the “Subject” and “Body” of the Email
  6. Select “Assignee” under “Issue members”
  7. Save the post-function
2. Click on "Save"
3. Publish the workflow. |
</details>

## [Set field value](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465504849)

<span style="color: #091e42">A workflow post-function that sets the value of a selected field of the target issues to the specified value</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Assign a reopened issue to the last person who last commented it.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the **Reopen** transition of the issue's workflow.
- Select the `Assignee` field.
- Write the following content in the `Value` section |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the **Create **transition of the issue's workflow.
- Select the Watchers field.
- Write the following content in the `Value` section |
</details>

####   
:light_bulb_on: Set the due date to today's date

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition.
- Select the `Due date` field.
- Write the following content in the `Value` section. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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.
- Write the following content in the `Value` section. |
</details>

#### :light_bulb_on: Assign the issue to the current user when the issue is being self-reviewed.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition that leads to the **Self-reviewed** status.
- Select `Assignee` field.
- Write the following content in the `Value` section |
</details>

#### :light_bulb_on: On the reopen of an issue, if a user is selected in the transition screen, verify that the user belongs to the Approvers. If not, assign the issue to the first user of the Approvers field.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition that leads to the **Reopen** status.
- Select `Assignee` field.
- Write the following content in the `Value` section |
</details>

#### :light_bulb_on: On the approval of an issue, append the current user to a multi-user picker custom field only when the current user is listed in "Approvers" field list.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the **Approve **transition of the issue workflow.
- Select the **Approved By **field.
- Write the following content in the `Value` section.
- Select the `Add value(s) to the field` option. |
</details>

#### :light_bulb_on: On creating an issue, add it to the first active Sprint of the board the issue belongs to.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition **Create.**
- Select `Sprint` field.
- Write the following content in the `Value` section |
</details>

####   
:light_bulb_on: Set the due date to issue created plus five days

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition **Create.**
- Select Due date field.
- Write the following content in the `Value` section |
</details>

#### :light_bulb_on:<span style="color: #000000"> On the creation of an issue assign the issue to the current user only if the user belongs to the Administrators group.</span>  


<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the Create transition
- Select the `Assignee` field.
- Write the following content in the `Value` section
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition`. |
</details>

#### :light_bulb_on:<span style="color: #000000"> Copy Jira service desk customers in a multi-user picker field to Request Participants ignoring the reporter of the issue</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Request Participants` field.
- Write the following content in the `Value` section |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Component/s` field.
- Write the following content in the `Value` section |
</details>

#### :light_bulb_on: Set the Original estimate of the issue to the difference of its creation date and Due date

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Original Estimate` field.
- Write the following content in the `Value` section |
</details>

#### :light_bulb_on:<span style="color: #000000"> Set the priority of the issue to Highest if the issue belongs to the "Customer Portal" component</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Priority` field.
- Write `Highest` in the `Value` section
- Write the following in `Conditional execution` |
</details>

#### :light_bulb_on: Assign the issue to the Project lead, if the issue is unassigned on creation

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Assignee` field.
- Write the following in the `Value` section
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition` |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Affects Version/s` field.
- Write the following in the `Value` section
- Select "Treat value as JSON" option |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Component/s` field.
- Write the following in the `Value` section
- Select "Treat value as JSON" option |
</details>

#### :light_bulb_on:<span style="color: #000000"> On the creation of a Story, change its priority to that of the Epic if the Epic's priority is lower than the current priority of the Story</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Priority` field.
- Write the following in the `Value` section
- Select "Ignore empty values" option
- Select "Treat value as JSON" option |
</details>

####   
:light_bulb_on: On the creation of a Story add the reporter of its Epic to the Watchers

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Watchers` field.
- Write the following in the `Value` section
- Select "Add value(s) to issue" option |
</details>

####   
:light_bulb_on: On creating an issue, Copy the component leads of the selected components to a Multi-user picker field

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the `Multi-user picker` field.
- Select the `Add value(s) to issue `option
- Write the following in the `Value` section
- Select "Add value(s) to issue" option. |
</details>

####   
:light_bulb_on:<span style="color: #172b4d"> </span>Add the members of the group selected in a custom Single-Group picker to the Watchers of the issue

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition of the issue's workflow.
- Select the Watchers field.
- Write the following content in the `Value` section.
- Select `Add source value(s) to the destination` `field` option. |
</details>

#### :light_bulb_on:<span style="color: #172b4d"> Identify all comments made between transitions A and B and add them to a custom text field</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - 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.
- Write the following in the `Value` section
- Add the *Set field value *post-function to the transition B
- Select the `Date of Transition B` field.
- Write the following in the `Value` section
- 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 |
</details>

#### :light_bulb_on:<span style="color: #172b4d"> S</span>elect the Installation tasks in the Checkboxes/Multi-select type field when all the Installations are done

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the Checkboxes field.
- Write the following in the `Value` section |
</details>

#### :light_bulb_on:<span style="color: #172b4d"> Add the time spent during the rework on an issue in the Rework Hours custom field, every time a rework is performed on the ticket</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition that leads to testing after Rework
- Select the `Rework Hours` field.
- Write the following in the `Value` section |
</details>

#### :light_bulb_on: Set the Assignee of the issue based on the selected office

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the “Create” transition
- Select the `Assignee` field.
- Write the following in the `Value` section
- Save the post-function and publish the workflow<br>> ⚠️ If you have a lot of combinations, it is recommended to create a Shared Nunjucks template (because of [this](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465241739)) and then use it in the post-function configuration. |
</details>

#### :light_bulb_on: 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.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the post-function *Set field value *to the **Create **transition of the Story workflow.
- Select the “Target Issues” as “Epic of the current issue”
- Select the *Man hours* field.
- Write the following content in the Value section. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the Description field.
- Select the “Target Issues” as “Parent issue of the subtask”
- Write the following content in the `Value` section |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *to the **Create **transition of the subtask's workflow.
- Select the `Due date` field.
- Select the “Target Issues” as “Parent issue of the subtask”
- Write the following content in the Value section.
- Write the following content in the Conditional execution section. |
</details>

####   
:light_bulb_on: 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.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition of the issue's workflow.
- Select the “Target issues” as “Issues linked to the current issue through the following link type”
- Select “duplicates” as the “Issue Link”
- Select the `Components` field.
- Write the following content in the Value section.
- Write the following content in the Conditional execution section. |
</details>

####   
:light_bulb_on: Set the assignee of the linked issues with the current user only if the user is the Developer of the linked issue.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition you wish to.
- Select the “Target issues” as “Issues linked to the current issue through any link”
- Select the `Assignee` field.
- Write the following content in the `Value` section
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition`. |
</details>

## [Set field value from user entity property value](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466257282)

<span style="color: #091e42">A workflow post-function that sets the value of a selected field of the current issue to the value of a User Property of the current user.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Store the Country, Department, Location, and Pin information of the Reporter of an issue into the issue itself while creating it.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Create a user entity property to store the Country information.
- Add the *Set field value from user property value *post-function to the **Create **transition of the issue's workflow.
- Select the field to which the Country information is supposed to be copied.
- Repeat the above steps for all the other fields. |
</details>

## [Set field value of linked issues post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323396) - Deprecated - Use [Set field value](/wiki/spaces/MWECS/pages/78481302) instead

#### :light_bulb_on: 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.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the post-function *Set field value of linked issues *to the **Create **transition of the Story workflow.
- Select the *Man hours* field.
- Choose the issue link type `has Epic` and write the following content in the Value section. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value *post-function to the transition
- Select the Description field.
- Select `is Subtask of` in the Issue link type
- Write the following content in the `Value` section |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value of linked issues *to the **Create **transition of the subtask's workflow.
- Select the `Due date` field.
- Choose the issue link type `is Subtask of`
- Write the following content in the Value section.
- Write the following content in the Conditional execution section. |
</details>

####   
:light_bulb_on: 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.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value of linked issues *post-function to the transition of the issue's workflow.
- Select the `Components` field.
- Choose the issue link type as `duplicates`
- Write the following content in the Value section.
- Write the following content in the Conditional execution section. |
</details>

####   
:light_bulb_on: Set the assignee of the linked issues with the current user only if the user is the Developer of the linked issue.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Set field value of linked issues *post-function to the transition you wish to.
- Select the `Assignee` field.
- Write the following content in the `Value` section
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition`. |
</details>

## [Shared Action post-function](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466323396)

<span style="color: #091e42">A post-function that runs an Action (a sequence of one or more JMWE post-functions), created in the </span>[Shared Actions](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466288975)<span style="color: #091e42"> page, on the target issues.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Setting multiple field values on the Create transition of every workflow of the instance</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| 1. Go to Manage apps → Jira Misc Workflow Extensions - >Shared Actions
2. Click on "New Shared Action"
3. Name it - "Set fields"
4. Click on "Add post-function"
  - Add the Set field value post-function and configure it to set a field value
  - Click on "Save"
  - Repeat step 4 and add all other post-functions
5. Click on "Save"
6. Go to the "Create" transition of a workflow
7. Add the "Shared Action" post-function
8. Select "Set fields" shared action
9. Click on "Save"
10. Publish the workflow
11. Repeat the same with the "Create" transitions of all other workflows. |
</details>

## [Transition issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242612)(s)

<span style="color: #091e42">A workflow post-function that triggers a transition on the target issues. This can be used to an issue one step further in the workflow.</span>

**Sample use cases:**

#### :light_bulb_on:<span style="color: #172b4d"> Start the progress on an issue immediately after its creation. </span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the **Create **transition of the issue's workflow.
- Input the transition name or ID.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: Automatically escalate an issue if it is being raised with a "Blocker" priority.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the **Create **transition of the issue's workflow.
- Input the transition name or ID of the transition that escalates the issue.
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Write the following content in the `Condition` section.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on:<span style="color: #000000"> Start the progress on an issue immediately after its creation if the reporter of the issue is a Project Manager.</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the **Create **transition of the issue's workflow.
- Input the transition name or ID.
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition`.
- Place this post-function at the end in the list of post-functions. |
</details>

#### :light_bulb_on:<span style="color: #172b4d"> Transition an issue only when all the Business Approvers approve the request through a comment "Approved"</span>

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the transition of the issue's workflow.
- Input the transition name or ID.
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Type the following code in `Condition`
  
- Place this post-function at the end in the list of post-functions. |
</details>

#### :light_bulb_on: All the cloned issues of an issue should transition through the workflow in parallel with the current issue.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to all the transitions of the workflow**, **except the **Create** transition.
- Select “Target issues” as “Issues linked to the current issue through the following link type”
- Select “clones” as the “Issue Link”
- Input the transition name or ID.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: We use Jira as our internal and external issue tracking system. Every client has his project to log issues into. If the issue is valid, the product owner creates a bug in the internal project and links it to the external issue. I want to automate the closing of external issues when its linked bug in the internal system is closed.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the **Close** transition of the workflow.
- Select “Target issues” as “Issues linked to the current issue through the following link type”
- Select “clones” as the “Issue Link”
- Input the respective transition name/ID.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: Automatically transition the Epic when all Stories are resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) *post-function* *to the **Resolve **transition of the Story workflow.
- Select “Target issues” as “Epic of the current issue”
- Input the transition name or ID of the **Resolve **transition.
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Write the following content in the `Condition` section.
- Place this post-function at the end in the list of post-functions.<br>Note that you might need to adjust the Status name in the script above to the status in which all Stories should be to transition the Epic. |
</details>

####   
:light_bulb_on: Resolve a support request when the bug blocking it is Resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) *post-function to the transition **Resolve** of the Bug workflow.
- Select “Target issues” as “Issues linked to the current issue through the following link type”
- Select “blocks” as the “Issue Link”
- Input the transition name or ID of the **Resolve **transition of the support workflow.
- Select `Resolution` from the field list under the `Transition screen` section.
- Select `Copy value from current issue.`
- Place this post-function at the end in the list of post-functions. |
</details>

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) post-function *to the **Start Progress** transition of the workflow.
- Select “Target issues” as “Parent issue of the subtask”
- Input the respective transition name/ID.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: Block the parent from being transitioned until all its subtasks are resolved and automatically transition the Parent when all Subtasks are resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition issue(s) *post-function* *to the **Resolve **transition of the Sub-task workflow.
- Select “Target issues” as “Parent issue of the subtask”
- Input the transition name or ID of the **Resolve **transition.
- Place this post-function at the end in the list of post-functions.
- Add the Sub-task blocking condition to the "Resolve" transition of the Parent workflow. |
</details>

## [Transition linked issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/466257658) - Deprecated - Use [Transition issues(s)](#) instead

A workflow post-function that triggers a transition on all issues linked to the current issue through a selected link type.

**Sample use cases:**

#### :light_bulb_on: All the cloned issues of an issue should transition through the workflow in parallel with the current issue.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition linked issues post-function *to all the transitions of the workflow**, **except the **Create** transition.
- Input the transition name or ID.
- Choose the link type as `clones`.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: We use Jira as our internal and external issue tracking system. Every client has his project to log issues into. If the issue is valid, the product owner creates a bug in the internal project and links it to the external issue. I want to automate the closing of external issues when its linked bug in the internal system is closed.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition linked issues post-function *to the **Close** transition of the workflow.
- Input the respective transition name/ID.
- Choose the link type as `clones.`
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: Automatically transition the Epic when all Stories are resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition linked issues *post-function* *to the **Resolve **transition of the Story workflow.
- Input the transition name or ID of the **Resolve **transition.
- Select the **belongs to Epic** link type
- Select the Conditional execution check box `Run this post-function only if a condition is verified`.
- Write the following content in the `Condition` section.
  
- Place this post-function at the end in the list of post-functions.<br>Note that you might need to adjust the Status name in the script above to the status in which all Stories should be to transition the Epic. |
</details>

####   
:light_bulb_on: Resolve a support request when the bug blocking it is Resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition linked 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 `Resolution` from the field list under the `Transition screen` section.
- Select `Copy value from current issue.`
- Place this post-function at the end in the list of post-functions. |
</details>

## [Transition parent issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465242394) - Deprecated - Use [Transition issues(s)](#) instead

A workflow post-function that triggers a transition on the *parent issue* of the current issue.

**Sample use cases:**

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

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition parent issue post-function *to the **Start Progress** transition of the workflow.
- Input the respective transition name/ID.
- Place this post-function at the end in the list of post-functions. |
</details>

####   
:light_bulb_on: Block the parent from being transitioned until all its subtasks are resolved and automatically transition the Parent when all Subtasks are resolved.

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Transition parent issue *post-function* *to the **Resolve **transition of the Sub-task workflow.
- Input the transition name or ID of the **Resolve **transition.
- Select the **is Subtask of** link type
- Place this post-function at the end in the list of post-functions.
- Add the Sub-task blocking condition to the "Resolve" transition of the Parent workflow. |
</details>

## [Unlink issues from the current issue](https://appfire.atlassian.net/wiki/spaces/JMWEC/pages/465504784)

This post-function is used to <span style="color: #000000">unlink issues from the current issue based on the result of a Groovy condition.</span>

**Sample use cases:**

:light_bulb_on:**<span style="color: #000000"> On rejection of an issue, unlink all its linked issues</span>**

<details>
<summary>Steps</summary>

|  |
| --- |
| - Add the *Unlink issues from the current issue *post-function* *to the **Reject **transition of the workflow.
- Write `true` in Condition |
</details>