Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This was only a bit of JSU in action. Subscribe to our YouTube channel and Access more JSU use cases.
See also the app documentation for some more examples and configuration screenshots.

...


Panel
bgColor#f5f5f5
titleColor#ffffff
borderWidth0
titleBGColor#000000
titleJSU for Jira Server/Data Center

This is the documentation of JSU for Jira Cloud. If you are using JSU on Jira Server/Data Center, you can find the documentation here.

(tick) Maintain consistency across projects and get a clear view of your team's tasks

Do you want to make your parent issue close when all the issues in it are closed?

JSU Automation suite for Jira workflows can help you automate it.

Check how to set up the JSU post-function 'Linked transition'.

Image Removed

Check out the "How to" video further below to configure your automation.

How to configure this workflow

  1. Go to your project settings and click to edit your workflow. Choose the transition you want to add your post function in. In this case we will choose the ‘Done’ transition number 31. Change to the post functions tab and add a post function. Choose the ‘Linked transition’ post function from the menu and add it.

  2. Now configure your post function. You want your epic to turn to done when all tasks are done, so choose your transition to be triggered on Epic. Choose the transition you want the epic to perform when the issues are done. Here we want the epic to turn to Done too. Make sure you choose the Done transition with the corresponding number – here it’s 31. You don’t need to add a resolution to the done transition. In case you want one, you have to make sure that the resolution field is visible on the transition screen.

  3. Since we only want to close the Epic when the last task is closed, we need to configure the status of the sibling issues. In this case we choose the status “Done” so that the linked transition will be executed only if all tasks in the Epic are done. Click add to move on with your JSU automation and publish your workflow.

  4. Now go to your Epic and turn all the tasks to “done”. Your epic status is now “done” too! You can configure the same automation process for any parent and sub-tasks you need.

...

Watch this video to see all of this in action*:

Widget Connector
width600
urlhttps://www.youtube.com/watch?v=2bu76MdsZb8
height350



Info

NOTE: This guide starts from the "Edit Workflow" screen of a chosen project. If you're not sure how to get to this page, follow the onboarding steps first on either: Edit the workflow of a new project or Edit the workflow of an existing project


(tick) Keep your backlog clean by ensuring parent issues are automatically closed when all of its sub-tasks are completed


↓ Follow the visual step-by-step guide below to see how to configure this automation in your Jira instance. ↓


  1. If you haven't already, switch the workflow viewer into "Diagram Mode"

    Image Added

  2. As we want to close parent issues when its' sub-tasks are done, we need to add the rule specifically to when issues transition to the 
    Status
    colourGreen
    titleDONE
     status. Click on the arrow that points inwards to this status to show the transition rule menu.

    As we want to add a Post-Function to this transition, which runs an automation after the issue has been transitioned to the target status. Select "Post Functions" from the list which opens a new tab.

    Image Added

  3. In the Post Functions table - click "Add post function" to view all available post-functions.

    Image Added

  4. Choose "Linked Transition (JSU)" and then click "Add" at the bottom of the screen.

    Image Added

  5. As we want the parent to be automatically closed when the last sub-task is Closed - let's set "Trigger transition on all issues related as" to "Parent / Sub-Task > Parent (Issue in Transition must be Sub-Task)".

    Image Added

  6. Now, we have to tell JSU which transition and in which workflow do we want to transition the Parent issue we just selected. As we want to keep this rule simple, we only want this rule to apply to issues in our "JSU" project. So for "Transition" we select the workflow that applies to our JSU project and the "Done" transition. This means any parent issues will be transitioned to 
    Status
    colourGreen
    titleDONE
     as part of the rule we're configuring.

    Image Added

  7. But remember, we only want the parent to be transitioned to 
    Status
    colourGreen
    titleDONE
     if ALL of it's sub-tasks are also 
    Status
    colourGreen
    titleDONE
    . To configure this, for "All other sibling issues (for example linking to the target with the same link type) must have one of the following statuses" we're going to set this as "Done".

    Image Added

  8. The remaining fields are optional. For your reference though we can talk about how you might want to use the remaining fields. If you're happy as is, feel free to proceed to Step #9.
    1. Resolution - If you would like to add a Resolution to the parent issue after the post-function closes it, you can define which Resolution to choose in this field.
    2. Perform as user - In Jira Cloud, all "actions" both manual and automated, must be performed by a registered Atlassian account. If you'd like JSU to impersonate another user to run its automation, you can choose that user here. It's important to note that the impersonated user must have the right account privileges to perform the action. If you're not sure, just leave this field blank. Leaving the field blank means the automation will be ran as the "JSU add-on user" which has elevated privileges and can perform most functions.
    3. Copy field - If you'd like to add more information to the parent issue as part of the automation, you can describe what information you'd like to add here.

  9. Now you're ready to save your new Post-Function. To do this, click "Add" at the bottom of the page.

    Image Added

  10. You can now see a preview summary of all your Post-Functions applied to this transition. To confirm this new workflow and test it out, you need to publish it. At the top of the screen click "Publish Draft" and then either "Yes" or "No" if you'd like to save a backup of the workflow before our changes are applied, followed by "Publish" again. 

    Image Added

  11. Now we can go test the post-function in action! Head to an open issue that has one or more open sub-tasks within it.

    Image Added

  12. Now proceed to transition all of the subtasks to 
    Status
    colourGreen
    titledone
    .

    Image Added

  13. Now refresh/reload the parent issue. You'll notice that it has now also been transitioned to 
    Status
    colourGreen
    titledone
     - which means our Post-Function has worked as expected!

    Image Added

  14. Congratulations! You've just configured your very own automation! (star)

    Feel free to continue exploring other use-cases for this Post-Function, such as "Close parent Epic when all the issues within the Epic are done" and more!


Need more Information or help? Get in touch!