Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practice: project automation or workflow trigger automation?

Hi!!

We have two options to create automated triggers between statuses (when PR is created, merged, closed...): edit the workflow and add a automated trigger to a transition OR create a project automation rule to do the same thing.

Is there a best practice to choose one or another?

 

2 answers

1 accepted

1 vote
Answer accepted
Guilhem Dupuy Community Leader Jan 20, 2021

Hi @Ellis Carvalho , 

As a mater of fact there is no bad practice in both of these options; my opinion would be to create an Automation rule in order to keep the Workflow as simple as possible in case  you intend to reuse it in another project one day, but adding a trigger in the Workflow is also good otherwise.

I am not quite sur of what you call an "automated trigger", maybe you could explain it to me so that I can be a bit more specific ?

Thanks, @Guilhem Dupuy  !

I meant adding a trigger to a transition inside workflow configuration. I think you understood correctly, given your answer.

And I liked your opinion, it's a good point! However, if I want to use the workflow in another project, I probably would want the automations too. So I'm always confused about which option to choose, you know?

Anyways, I know it depends on many factors and probably there isn't a right answer to that, so thanks again for your point of view! :) 

Hi @Ellis Carvalho 

"Yes, and..." to what @Guilhem Dupuy  and @John Funk are saying: there are no best practices here, only better ones for different situations.

Each of these tools can help solve automation needs, and what you problem you are solving may drive which to use.  For example, to limit a status transition workflow seems better.  For automating notification or system interaction (Slack, DevOps, etc.), rules may be better.

Please consider looking over the examples in this community forum or the examples from Atlassian to get ideas of how to solve problems.  For example, here is the library of automation rule examples:

https://www.atlassian.com/software/jira/automation-template-library#/label/all/1453

Best regards,

Bill

Like Ellis Carvalho likes this
1 vote
John Funk Community Leader Jan 20, 2021

Hi Ellis,

I agree with @Guilhem Dupuy  - there's probably no bad practice either way. If you are limited on the number of rules you can execute with Automation for Jira, then you might consider using post functions and triggers on the workflow. Otherwise, Automation allows you to not have to add the functionality to every workflow, but can be done more globally. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

639 views 10 16
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you