Automation - making rules for complete workflow

[Jan Šimek]

Hi I have tried to make a one automation rule, which goes through all workflow, but it did not work, because from what I did understand it was missing triggest points. So I did create a several of them, which does not look precious, but works as it should. But now I am wondering if there is no other way, because it can be mess in the future. Not sure how effective is to make a automation rule for every transition there is.

Maybe you can help me?

Thank you

[Bill Sheboy · Accepted solution]

Hi @Jan Šimek 

Would you please provide more details about your use case/the problem you are trying to solve?

For example, when there are specialized actions to take for each transition it may make sense to have separate automation rules...and when there is a common action for multiple transitions fewer rules could suffice.

Perhaps posting images of your rule(s) and the workflow will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill

[Jan Šimek]

HI, thanks for answer, posting my workflow and rule, which i tried to build upon it. The rule is quite long so it has to be in 3 different pictures. I have changed a bit a workflow from then, so it is not actually up to date, but anyway it still did not work. If I remember correctly it stopped by status IN NEGOTIATION and I could not find a way it to work.

[Bill Sheboy]

Thanks for those screen images, @Jan Šimek 

First thing: please try to keep to one thread in the discussions as that will help others see when there are multiple answers to solving your question.  Thanks!

Next, please consider looking for a browser addon to capture the full scrolling page.  That can prevent getting pieces of the rule images out of order for your questions.

Okay...back to your question:

Your rule seems to be triggered on Issue Created, and then tries to process multiple things based on things happening later, like changing status or the values of Approval.  And then it checks different and contradictory conditions.  That is not now automation rules work...

When something happens to an issue, it triggers an event, which a rule can "see" and then take action.  For example, you may want a rule trigged on Issue Transitioned (changed status) to DECLINED or LOST, and then take appropriate actions.

Please pause to consider which events you want to "see" and what actions you want to take, and then build your rules one by one for the different cases.  It may be possible to combine some rules when the triggering event is the same.

After you have tried to do that for some cases, and if you still see problems the community can offer ideas.

To get you started, please take a look at this documentation and rule examples to give you some ideas:

• https://www.atlassian.com/software/jira/guides/expand-jira/automation
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20
• https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465

Thanks!

[Jan Šimek]

Thank you :-) I though it will be like this. 

[Jan Šimek]

HI,

thanks for answer, posting my workflow and rule, which i tried to build upon it. The rule is quite long so it has to be in 3 different pictures. I have changed a bit a workflow from then, so it is not actually up to date, but anyway it still did not work. If I remember correctly it stopped by status IN NEGOTIATION and I could not find a way it to work. Maybe you could help?