Moving a Sub-Task to In Progress does not Transition its Parent's to the Same Status
プラットフォームについて: Cloud、Server、および Data Center - この記事はすべてのプラットフォームに等しく適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
The content on this page includes steps to extend Atlassian software with third party apps, and therefore is not covered by our Atlassian Support Offerings.
Steps on How to Improve This Feature
Ensure that you have the Misc Workflow Extensions plugin installed in your instance.
- Edit the workflow associated with the reported project.
- Add a new post function called Transition parent issue to the Start Progress transition.
- Add the ID of the Start Progress transition to the Transition: field:
- Ensure the Post-Function is displayed on the transition per the example below:
- Apply steps 3 and 4 to the following transitions to make the whole thing seamlessly:
- 進行停止
- reopen
- Reopen and start progress
- Publish the newly enhanced workflow.
More information on how to add post functions can be read from here. Documentation for the Transition parent issue post function can be read from here.
Testing the Feature
Now, attempt to transition issues from one column to the another column in Work Mode. As long as you're transitioning a sub-task from a list of sub-tasks, you will notice that the parent issue's status will follow the moved sub-task's status:
