Automation - Linked Issues

[Sean Wood]

Dear all,

Trying to create an automation that prevents an issue from moving status unless all linked issues are complete.

Outline below:

I have 3 Issues types and One Epic. Each of them would be considered to be a story level issue (i.e. No Subtasks).

Epic (Product)

Deliverable (Product Specific)

• Defect (Product Specific)

Global Defect - related to more than one deliverable across multiple products.

• Defect issues are linked to more than one Deliverable issue - as they relate
• Global Defect issues are linked to multiple Deliverables across products.

The basic idea is:

If issues linked to a Deliverable are not complete (regardless of if they are Defects or Global Defects), the Deliverable should not be able to be moved from XXX status to YYY status.

I'm unsure of exactly how to approach this.

I've attached my attempt at the Automation but I seem to be lacking knowledge of how to manage the check the linked issue status.

Any help would be greatly appreciated.

Cheers,

Sean.

[Stefan Salzl · Accepted solution]

Hi @Sean Wood ,

as far as I got your requirement right I‘m afraid it won‘t fully be covered by an automation rule.

In order to check conditions before an automated transition (so transition should only be done by automation rule when all linked issues are done) —> thats fine.

The thing is: This won‘t prohibit to transition the issue manually. If this should be the case then I guess workflow conditions is the festure of your choice (this is mainly the feature to do checks while transitioning through workflow, tbh: i dunno if checking for linked issues is possible).

Best
Stefan

[Sean Wood]

@Stefan Salzlthank you for your input.

I seemed to have resolved it.

See attached PNG.

[Stefan Salzl]

I see. So as far as I understand it you allow the transition first, then check for the linked issue‘s status and if there are some linked issues open you transition back to the QA status and leave a comment?

Best
Stefan

[Sean Wood]

@Stefan Salzl  - yes. It seemed to be the only way to do it (at least that I could find). But in addition, so the person who moved the issue is aware, I at mention the initiator in the comments via automation just to ensure they are aware that the issue has transitioned back.

Cheers,

Sean.

[Stefan Salzl]

@Sean Wood ,

another way (i guess) would be to script the condition with scriptrunner (in case this plugin is installed in your jira instance).

Best
Stefan

[Sean Wood]

@Stefan Salzl  - Ah! If only this were the case. We are cloud based and have 400+ users. I struggle to justify the $550 a month for the license.

That said, appreciate the idea. I might try to collect a load of instances where this is useful and this may add up the license fee being justified :-)

[Stefan Salzl]

@Sean Wood 

I feel ya 👌🙌 pricing is always a reason.

In case your problem is solved please consider to click the accept button so that the question is marked as solved and is easier to find for other users with similar problems.

Best
Stefan

[Karyna Tyrnavska _SaaSJet]

HI, @Sean Wood 

As I’ve understood, you need to block some issues that are involved in one process. You can try Business Process Manager by SaaSJet team.

It allows blocking tasks unless the form isn't filled or the information in the forms isn't approved.

I Hope, it helps you!