Check for and close predecessors when creating scheduled tasks

[Philip Deubner]

Dear,

we switched from another scheduling plugin to Automation for JIRA. 

We are using it now (amongst others) to create issues on a scheduled base. Due to absences it may happen that the predecessing issue is not resolved before the next one is created.

Is there a way to either have Automation for JIRA checking if a created issue is still unresolved and to skip the creation of the new one OR create the new issue and resolve the older one with a defined solution.

Thank you for your support on this,

best regards,

Philip

[John McKiernan]

Hi Philip,

I'm not sure I fully understand your use-case here, but you can certainly use a 'Related issue condition' in Automation for Jira to check if a previous issue still exists.

So your rule would look something like this:

• Trigger: Scheduled
• Related issue condition with some JQL checking to see if the predecessing issue does not exist
• Action: Create issue

The bit I'm not sure about is how you find the related previous issue - depends on your use-case what JQL you'd need.

This is the condition you'd need to use: https://docs.codebarrel.io/automation/components/conditions/conditions.html#related-issues (but change related type to 'JQL')

Cheers,
John

[Philip Deubner]

Dear John,

thank you for your input. I honestly hoped for anyone having had the same idea and to come up with a "recipe", but this was seemingly to ambitious :-D.

I will play around with you idea, which is finally the other way round of what I was thinking.

Regards,

Philip

[John McKiernan]

No problem! Just let me know if you have any issues.

Cheers,

John