I added this add on with an evaluation license. The version is 3.1.0. I created a custom Sub Task and I am trying to use the following Post Functions:
Neither one of these are working. Any help here would be greatly appreciated.
can you elaborate on what you've tried? All this is clearly supported by the plugin.
I assume you've added the "Set Field Value From Parent" function to the workflow of the subtasks? And the subtasks are real subtasks (as defined by JIRA) and not linked issues?
Regarding transitioning the parent issue, you need to provide the Transition Name or Transition ID of the "Resolve Issue" transition (not step), and make sure it is the ID of thr transition in theparent issue's workflow (in case you don't use the same workflow on normal issues and subtasks).
Can you post screenshots of the transition screen (on the post-functions tab)?
I did have a parent transition associated with a transition screen (I had set this up at 2 different spots in the workflow) but after reading the doc when it wasn't working, I removed that one and left the one I sent you. The subtask is being set to Complete and the last subtask being completed, should update the parent issue to the status of "Ready".
I have not looked at the logs. I have not been shown how to do that yet. I'll have to ask someone I know who has.
Any other ideas, just let me know. Thanks.
Note that I'm not sure you will achieve what you want to achieve: if I understand correctly, you would like to transition the parent issue only when all subtasks have gone through the "Review complete" transition. This is not possible with the Transition Parent issue function. On the contrary, the first subtask going through the "Review complete" transition will transition the parent issue to "Code complete", which is probably not what you want.
In that case, you need to move the "Transition Parent Issue" to the bottom of the list, at least to after the "Set issue status...". Otherwise, the Condition you have put on the Parent issue transition ("Code Complete") will prevent the transition from taking place, as there will always be at least one sub-task that is not Resolved (the sub-task triggering the parent transition)
I did what you suggested and placed the "Transition PArent Issue" after "Set issue status..." and tried it again but it still didn't work. The parent issue just doesn't update. I'll try it again with a brand new issue and see if I experience anything different. If it works, I'll update it here.
I'm having a similar issue. I need the parent issue to transition when a sub-task is created, then to transition back when the sub-task is closed.
The last step works perfectly, but I can't get the parent to transition when the sub-task is first created. Is this a limitation of the plugin? I've tried changing the order of post functions during the create transition but it didn't make a difference.
Did you make sure that the transition you're trying to trigger on the parent is not associated with a transition screen, as explained in the plugin documentation? There is no limitation that prevents the function from working in a "close" transition, mostly because the Close transition is a "normal" transition (only the Create transition is special).
Hi there, I am having a similar issue. I want the status of the parent to use the transition "Ready for testing" when a test sub-task is created for it using the Create on Transition plugin, then transition back via "Ready for use" once the test sub-task is closed. The last step works fine, and the parent transitions, but I can't get it to transition the parent when the test sub-task is first created. Any ideas?
There is no transition screen, however I played with it a bit more - it works when a sub-task is manually created but not when it's created by the Bob Swift create on transition plugin.
I did come up with a workaround for anyone using both plugins (and different workflows for different issue types).
My project is tracking the movement of suits in and out of a high containment facility, with a requirement to test the suits every 5 uses. I have three workflows - one for the suit, one for the experiment and one for the suit testing. The suit is the parent issue, and sub-tasks are created for experiments and testing.
Every time an experiment is closed, the number of suit uses increments by 1. If the number of uses reaches 5 in the close transition of the experiment, a testing sub-task is created, I also wanted the create step of the testing sub-task to trigger a transition to a test status on the parent (suit) to ensure no one starts an experiment with it, and then to transition back once the testing task is closed, also resetting the number of uses to 0.
Everything worked except transitioning the parent on the create step of the test sub-task when the test sub-task was created automatically.
The very messy workaround I used is as follows:
When the conditions are correct to create a test sub-task from the experiment, I used the create on transition plugin to create a "related to" link between the experiment and the test sub-task, I then used the workflow extensions plugin to transition the linked issue to an arbitrary step (from a post function of the experiment), and on this transition I used the workflow extensions plugin to transition the parent.
I'm not sure which of the two plugins is causing the issue with post functions on the create transition.
I'm not sure I understand correctly. You are saying that the subtask is created automatically during a transition, and you are trying to transition the newly created subtask's parent during that creation? That would mean transitioning the parent task while it is already being transitioned. Something like:
Transition Parent -> create Subtask (in a workflow function of the Parent transition) -> Transition Parent (in a workflow function of the Subtask's Create transition)
It might work, but you must make sure that the Create Subtask function is done at the very end of the Parent transition.
Gaining insight into your team’s effectiveness and choosing the right estimation technique. Estimating projects is hard. It is because people have the tendency to underestimate the time thin...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs