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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,489
Community Members
 
Community Events
176
Community Groups

How many workflow post functions is too many?

Just curious from a management as well as a performance standpoint...

1 answer

1 accepted

1 vote
Answer accepted

I've seen transitions with almost 100.  They're very slow, but still work.

On top of the standard five, I would try to avoid adding more than 10-12 simple ones, or 2-3 complex (or dependent on other systems) ones if you want the transition to execute before your people get frustrated and impatient.

From a management point, working through a list of 70 "clever" things someone things they might need to do on a transition is a nightmare.  I'd rather have a couple that do some minimal stuff, and one that offloads the rest of the clever things as a single "Oi!  This just happened" to some middleware layer.

Thanks Nic, that makes a lot of sense. 

I'm curious--do you have guidelines or thoughts on when/why to build automation into post-functions vs. Automation/Automation for Jira?

Payne Rising Star Dec 30, 2019

100! Egad!

Like Nic Brough -Adaptavist- likes this

@Payne - yes, scary, and horrid to try to untangle.

@Andy J - I have no "simple" guidelines, it is absolutely "what will work for this team".  Do what works well for your people (not you as an admin - our job is not to be happy, but to enable other people to work well together, even when that particular config is really bad)

Like # people like this

I appreciate I am replying to an old response. But, @Nic Brough -Adaptavist- do you know of any Performance differences between Jira Automation and Post Functions?

Like Andy J likes this

Automations put more load on a machine, because they have to be triggered, inspected and then followed, often doing many complex things.  Post functions simply run when the transition is confirmed, most don't need to do any of the triggering and inspection work.

There is not that much in it, but note that for most Cloud systems, you only get a limited number of automation executions a month...

Like Andy J likes this

I see why the number is restricted on Cloud.

However, then on DC. Would you suggest that we need to somehow monitor automations and then suggest to users if some of them look like they could be moved to a post function? Because with Automation there is no control as such. A Project can just create hundreds of rules. :D

Yes, your admins should be checking up on the global list of automation to see what is being used heavily or lightly.  Something most places have baked into their monthly housekeeping routine.

Like Andy J likes this

Suggest an answer

Log in or Sign up to answer