Transiting linked issue which uses another workflow

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!

5 answers

Thanks for your suggestion, pareshkumar. I understand that there should be several ways to do the job. My question is if it's possible to do it using built-in post-function, which seem to be designed right for that purpose.

can you provide atlassian-jira.log file.

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.

Hi, In order to check if the problem is when issue and linked issue in diff workflows OR the issue is with linked issue workflow itself I'd also check the third case when both issue and linked issue use linked issue workflow. In this case workfliw is the same as in your first case. If it works then the problem is with workflow difference, check ids names transitions etc. If it doesnt work, then your linked issue workflow casing problems. One of the possible reasons could be a screen associated with the transions which expects some data. While the transion details are valid you might not be able to pass it the automated way.

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.

Then it is definitely a bug...

I'd raise a bug.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

45 views 0 4
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you