Linked Issues Status Condition (JMWE app) doesn't work as expected.

[Gregory Kremer]

Hello Jira experts. Need a second pair of eyes to review my Condition and let me know why it doesn't work.

The condition in question is placed on the transition to Completed (Done) Workflow status to close "Initiative" issue Type issue. It requires for all "child" Epics to be in the StatusCategory = Done (green) in order to do so. Here is how it looks like

But it doesn't work for me, and I don't see why. I also tried similar Validation but it didn't work either. Any suggestion as to why it is happening would be greatly appreciated.

[Evn Tomeny [Appfire] · Accepted solution]

Gregory,

At first glance, it looks to me like you may have chosen the wrong direction for the "is Parent of" link. Since the Initiative is the one you're trying to close, the Epics would be linked through the "is Child of" link type (I'm assuming that's what you've called it).

This might be confusing because what the condition is asking is, "How is the Epic linked to the current issue?" and what you see when looking at the Initiative is, "How is the current issue linked to the Epic?" - you'll want to click through to one of the Epics, then see which link it has back to the Initiative.

Let me know how that works!

Cheers,
Evn

[Gregory Kremer]

@Evn Tomeny [Appfire] Thank you for your reply. Unfortunately there is no "is child of" option there, or I would try it.

[Evn Tomeny [Appfire]]

@Gregory Kremer Click into one of the Epics, and see what the link back to the Initiative is called.

[Gregory Kremer]

@Evn Tomeny [Appfire] "Parent LinkI think that "is Parent of" is the correct option. Please take a look at the highlighted part of the description:

[Evn Tomeny [Appfire]]

@Gregory Kremer I think I see what's happening here. You're not actually looking at an Issue Link on the Epic - you're looking at the value in the Parent Link field created by Advanced Roadmaps. I should have realized that when you mentioned you were working with Initiatives.

Unfortunately, Jira Expressions (the language 3rd-party apps must use to implement custom Conditions and Validators in Jira Cloud) does not yet support the new unified issue hierarchy Atlassian recently introduced or the Advanced Roadmaps "Parent/Child" relationship.

So today, we can't support this specific use case. Sorry about that! You could still do this with typical Issue Links if you wanted, but it would require ensuring that each Epic were actually Linked to the Initiative. And what you've done here should work for issues that are part of an Epic.

[Gregory Kremer]

@Evn Tomeny [Appfire] Sorry, I am not sure what you meant by "You could still do this with typical Issue Links if you wanted, but it would require ensuring that each Epic were actually Linked to the Initiative." Does it mean that we need to use additional type of linkage from Initiative to Epic and from Epic to Bug, Story, Task? If yes, how would it look like, if I still can't use "is child of"? Could you provide an example? Thank you.

[Evn Tomeny [Appfire]]

@Gregory Kremer The method you're using should work fine for Epic -> Bug, Story, Task. It's only the Initiatives that break. I was guessing that you could use an actual Issue Link to link your Initiative to each Epic - something like Is Blocked By.

[Gregory Kremer]

@Evn Tomeny [Appfire] I got it. Thank you - it does work as expected for Epics. Do you have an ETA for this option to work with Initiative?

[Evn Tomeny [Appfire]]

Unfortunately, it's not up to us. This is something that Atlassian needs to support before we can make this work.

I did a quick search, but wasn't able to find any public info about if and when Atlassian plans to support this. Sorry!