Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

I have a question : How to get all added components as subtasks in Master Ticket creation in JIRA?

I'm trying to configure JIRA cloud to get all added components as sub tasks while Ticket/Issue creation but I'm only getting first 2 components only as subtasks. All other components are getting ignored. Where do I check this and how to get all added components as Subtasks ??? Please help.

1 answer

Hi @satish_cont24  -- Welcome to the Atlassian Community!

How are the first 2 subtasks (from components) being added currently?  If if this is by an automation rule you may want to check that for problems.

Best regards,


Hi @Bill Sheboy ,


I'm using Automation rule for creating subtask with added component names. and I'm using contains "equals" of condition. But I'm only getting how many subtasks I have mentioned in Action Rules in Automation (it's static).

But my requirement is to create subtasks dynamically for added components while Issue creation process. For example, if user creates an issue with 6 components then after creation, User should see 6 subtasks there with Components names.


Could you please provide in any way we can achieve this requirement. Thanks in advance.,

@satish_cont24 thanks for confirming, as I suspected that was your use case.

There is currently no built-in looping structure/component in automation for Jira  (A4J) that can support that.  There are similar posts in this community forum where the person ended up editing their rule when a new component type was added.  In those cases, people added components to the project prior to use in an issue.

The only work-around I can think of is to simulate a recursive rule using a custom field as a flag, although that sounds a bit risky given the potential performance and timing issues with automation rules.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

193 views 6 7
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