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

Is there an efficient way to generate sets of tasks based on an issue field?

I have a project where requests are logged for different areas of work.  Based on the area of the project, I have automations that generate sets of tasks linked to that request.

Currently, I have a number of automations that trigger on issue creation and check an issue field to determine what tasks to create.  This has led to dozens of automations running when an issue is created.  All but one will run in fractions of a second, but that's still time that adds up.

Because these tasks are being linked together in different ways based on which ones need to be done first, and we need for different sets of tasks per area, I cannot consolidate everything into single automation or use "Create sub-tasks".  

Is there a more efficient way to accomplish this?

1 answer

1 accepted

0 votes
Answer accepted

Hi @Ryan 

An approach seems related to what you are trying to improve.  For example,

  • Are you trying to reduce the number of automation calls per issue creation?
  • How soon after issue creation do you need the additional tasks/sub-tasks?
  • Etc.

Unfortunately, rules are limited to 64 components (I believe) so no ginormous rule to cover all cases with if/else... and there is no action yet to call-out to another rule, as a sub-routine, to divide and conquer.

One alternative would be to use scheduled triggers, JQL, and an indicator field to say "processed".  Such as:

  • Trigger: scheduled with JQL to select one area of work and for which the indicator is not set to "processed"
  • Action: add the tasks as needed
  • Action: set the indicator field to "processed" so it doesn't get processed again

You could schedule these as often as you believe you would need the tasks available.  And clone the rule for each area of work type.  The rules should only fire once per issue creation due to the JQL and the processed indicator.

Best regards,

Bill

My goal is to reduce total processing time.  With many automations firing when an issue is created, it feels like there's a lot of wasted time. 

 

I'm going to give a scheduled method a try.  That way, one will only run once a day rather than every time an issue is created.

 

Thanks for the idea!

Like Bill Sheboy likes this

Ryan, if this solution approach works out for you, please consider marking the question "answered"... that will help others in the community find answers faster to similar questions.

Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

768 views 17 21
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