Remove assignee when an issue moves back to To Do

Owned by Deborah Scott
Last updated: Nov 14, 2024
4 min read

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.

On this page:

On this page:

Goal

Remove the Assignee when an issue moves back to to do and transition all subtasks in progress back to to do .

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 to do. Because work is paused on the parent issue, you want to ensure that all subtasks in progress automatically move back to to do.

Components

Universal Rule Builder: Update Any Issue Field and Trigger a Linked Transition

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.

https://app.arcade.software/share/tJKwREa6yEXoh4Wzivqa

How to configure this rule

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

    Screenshot of Jira workflow editor in Diagram mode.

     

  2. We want the post function to run when an issue moves to to do. Click the arrow that points to this status to display the transition Options menu.

  3. Select Post Functions to display the Post Functions tab.

    Screenshot of Jira workflow editor showing post functions highlighted in the transition options menu.

     

  4. Select Add post function to view all available post functions.

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

     

  6. In the list of components, select the Update Any Issue Field post function.

     

  7. To configure the post function:

    1. From the Field Name drop-down list, select the field that you want to update following the transition. Here, we select Assignee.

       

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

       

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

     

  9. Click Add component.

  10. In the list of components, select Trigger a Linked Transition.

  11. Select The subtasks of the parent issue relation type option.

  12. Select the To Do status from the list of available statuses.

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

  14. Select Publish Draft at the top of the page. If necessary, you can save a backup before confirming.

Test the post function in the workflow

We recommend that you build and test your rules in a test project.

  1. Go to an issue in your project that is in progress or another status that can be transitioned back to to do. If you don’t have any, you can create one and select an assignee. Ensure that this issue has subtasks that are in in progress .

  2. Move the issue to to do.

  3. Refresh your browser to reload the issue. You'll see that the previous assignee has been removed and the issue is unassigned.

  4. Go to one of the issue’s subtasks that was in progress and confirm the status has changed to to do .


    Congratulations! You've just configured your very own automation with the Universal Rule Builder.