Linked Issues Condition and/or Validator Question

[MAG-II]

Hi Fidel -

I've come into a complicated step in my JIRA project. I'll do my best to explain what's happening.

I have 2 workflows (#1 and #2). Workflow #1 has two different transitions that create a clone and Issue link onto Workflow #2 (creates a clone of the Issue, but different Issue type). That works well. In one path where Workflow #1 creates a cloned Issue onto Workflow #2, I want to add some additional requirements.

What I want to happen is that the cloned Issue is not able to advance to the next status (in Workflow #2) unless it's Linked Issue has reached a specific (further) status in Workflow #1.

I know I can do this by adding Validators with Labels (in Workflow #2) and then updating Label for Linked Issues (from Workflow #1), but the problem is that there are two different paths in which the Issue can be cloned from Workflow #1, and I don't want both of the cloned Issues to have the same requirements.

I'm having trouble wrapping my head around where to even begin looking with the JWT features. Do you have any direction/advice you could lend me?

[MAG-II]

Figured it out! (sorry about that)

[Fidel Castro Armario]

Hi @michaelgayheart,

Maybe you can solve the problem by adding a mark to the cloned issues for distinguishing which path was used for cloning them. To do it you can add a hidden custom field (let's call it Cloning Path) you can set with 2 different values (let's use "A" and "B" as values) at the moment of issue creation depending on the transition that triggers the issue creation (issue cloning).

Then you can implement a validator in the cloned issue that only works when field "Cloning Path" has value "A". When field "Cloning Path" has value "B" the validator doesn't work.

If you have problems to implement the validator I can help you. You should attach the validator you are using now, and I will explain how to modify it.

[MAG-II]

Thanks for the response. I just used a Condition on Linked Issue Condition, and it seems to have solved my problem (for now). I will bookmark this ticket and go back over it when I run into more problems. As always, thanks for being so responsive and helpful.