I'm trying to automate transition of linked issues. The goal is to transit all "blocks"-linked issues of the current issue to the defined status. I'm using post-function "Transition linked issues" on original (blocker) issue's transition.
It works good if both issues - original blocker issue and linked issue being blocked - use same workflow. But if linked issue uses another workflow, it isn't transited. I suppose the reason is in the absence of transition with name/id specified in post-function I create in the linked issue's workflow.
But it doesn't look like correct behaviour, linked issue has it's own workflow with the transition names/ids, and I specify appropriate id for that linked issue's transition in the post-function. Why it cannot be transited?
Is it bug? Am I wrong?
Thanks for the reply!
Unfortunately, I don't have immediate access to the filesystem of Jira server. Though it's availiable on request from system admins.
What would you seek there? My question is not about the reason of the described behaviour. I would just clarify if it's known restriction and if so, I would get a reason of this restriction or write a bug in Jira's bugtracking system.
As I wrote above, it works good if both issues - original blocker issue and linked issue being blocked - use same workflow.
Sorry, Vasiliy, I didn't understand your suggestion clearly. But the third case you've mentioned is an exact description of the configuration I tried. And it works good.
There's no any screens associated with any mentioned transitions.
Situation is simple:
All blocks-linked issues always use workflow A.
if I close an issue, which uses workflow A, all blocks-linked issues in a defined status are auto-transited.
if I close an issue, which uses workflow B, all blocks-linked issues in a defined status are NOT auto-transited.
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