I am using same work flow for both parent Task and sub-task and tried to use the above said post function (i,e "Transition Parent Issue") when the issue state transitions from "In Progress to Done" state as below.
Update parameters of the Transition parent issue Function for this transition.
Type the name or ID of the transition to trigger on the parent issue.
And I started transitioning the sub-task state from To Do to In Progress and then in-turn transitioned to "Done" state. But parent task is in To Do State only even after moving the sub-task status from In Progress to Done state.
I am not sure why it's not moving parent task status from To Do to Done.
whether there is any issue in using/sharing the same workflow for both parent and sub-tasks for a specific Issue Type?
What would you recommend for JIRA Cloud users? The JIRA Misc Workflow add on will no longer be available after 7/31/2016.
I have 2 separate WFs - 1 for subtasks; 1 for stories - that are pretty similar (to do -> in prog -> done). I need the parent issue to transition to it's subtasks' corresponding status when the subtask is transitioned. I do not have a 'transition parent' post function anymore, or anything that corresponds to this type of function.
@Jamie Roberts please check out this link – https://confluence.atlassian.com/jirakb/jira-miscellaneous-workflow-extensions-jmwe-removal-from-jira-cloud-815262011.html
It details the removal of JMWE. Specifically, David Fischer is creating most of the Post-Functions in his previous add-on in a new, Connect-compatible add-on.
We are doing everything we can to mitigate the final impact to customers:
- Atlassian will re-implement several of the most popular conditions and validators as native JIRA functionality. We plan to provide a seamless automatic migration where possible.
- The developer of the original JMWE add-on will provide a new add-on that offers many of the same post-functions. You will be able to install this add-on on your instance and migrate to the replacement post-functions.
I do not know. You may consider reaching out to David Fischer from Innovalog. He can answer and he is very fast.
Personally, I would imagine it will be paid.
The old Misc Workflow Extensions is not free... It hasn't been free for JIRA Standalone customers, but it has been included in JIRA Cloud subscriptions because nothing added functionality like it. I suppose it was just deemed necessary in the past.
Now that Atlassian is (finally) implementing the majority of the functions themselves, they can remove the 'free but not free' add-on from JIRA. Unfortunately, they are not implementing the Transition Parent function themselves .
Well, that's neither here nor there. Obviously if you buy an add-on for a single function, you might feel like you're not a good deal. Furthermore, JIRA being so flexible, is hounded constantly by "what people feel like should be included." JIRA is appealing because it can easily model a variety of business processes but that doesn't mean it caters to all of these business processes.
Your options are to check out one of the dozen or so scripting add-ons or to write a post-function yourself. Some of these approaches are free but JIRA is pretty extendable regardless. You do need to know a thing or two to implement though.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot