| Info |
|---|
This is the documentation for JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, see our JSU Server/Data Center documentation. The Universal Rule Builder is available only in JSU Cloud. |
...
Goal | Remove the Assignee when an issue moves back to
| ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Scenario | You identify a change in priorities. Progress on an issue may need to be paused or stopped entirely so you want the Assignee field set to Unassigned when the issue moves back to
| ||||||||||||||
Components | Universal Rule Builder: Update Any Issue Field and Trigger a Linked Transition |
| Tip |
|---|
This setup uses the Universal Ruler Builder. Here you can see how simple it is to configure two different post functions in one place. |
Example setup
Follow the interactive demo to learn how to set up this use case, or follow the numbered steps below.
...
How to configure this rule
Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in Edit a Jira Workflow. You can then view your workflow in Text or Diagram mode. The steps in this use case represent Diagram mode. If you haven't already, switch the workflow viewer to Diagram mode.
We want the post function to run when an issue moves to
. Click the arrow that points to this status to display the transition Options menu.Status title to do Select Post Functions to display the Post Functions tab.
Select Add post function to view all available post functions.
Select the Access the Universal Rule Builder from JSU post function, then click Add at the bottom of the page. The Universal Rule Builder displays.
In the list of components, select the Update Any Issue Field post function.
To configure the post function:
From the Field Name drop-down list, select the field that you want to update following the transition. Here, we select Assignee.
In the Assignee field, select the new value that you want to assign to the field when the transition is complete. Here, we select Unassigned.
In the rule overview, enter a name for the rule. Choose a name that helps you identify the rule, for example,
Update assignee to Unassigned.
Click Add component.
In the list of components, select Trigger a Linked Transition.
Select The subtasks of the parent issue relation type option.
Select the To Do status from the list of available statuses.
Select Add at the bottom of the page. A summary of all your post functions applied to this transition is displayed in the draft workflow.
Select Publish Draft at the top of the page. You can choose to If necessary, you can save a backup if required before confirming.
Test the post function in the workflow
| Noteinfo |
|---|
We recommend that you build and test your rules in a test project. |
Go to an issue in your project that is
or another status that can be transitioned back toStatus colour Blue title in progress
. If you don’t have any, you can create one and select an assignee. Ensure that this issue has subtasks that are inStatus title to do
.Status colour Blue title in progress 
Move the issue to
.Status title to do Refresh your browser to reload the issue. You'll see that the previous assignee has been removed and the issue is unassigned.
Go to one of the issue’s subtasks that was
and confirm the status has changed toStatus colour Blue title in progress
.Status title to do 
Congratulations! You've just configured your very own automation with the Universal Rule Builder! .