Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

How do I get the User Story's Component values to be automatically added to its Subtasks?

Hey everyone!

So, in my project we have quite a few different teams/boards and also different Components values (Component field inside the Card).

We are sort of suffering with having to add to all the subtasks the same Components previously added to the User Stories, because they can be quite a few.

Is there an Automation I could create in Jira to every time I create a User Story its components values go automatically to its subtasks when they are created?


Thanks in advance!

 

2 answers

1 accepted

0 votes
Answer accepted
Michel Neeser
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 20, 2023

Hi @Lucas Ferreira

A rule like the following should work for your use case. It adds the components from the parent issue (if there are any) to the subtask after creating the subtask:

Automation_-_Jira.pngAutomation_-_Jira-2.pngAutomation_-_Jira-3.png

Hope this helps.

Hey @Michel Neeser , that worked! Thank you so much!

Michel Neeser
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 20, 2023

@Lucas FerreiraGlad I could help! Please consider accepting the answer, maybe it is helpful for others as well. Thank you!

Like Lucas Ferreira likes this
0 votes
Stephen Wright _Elabor8_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 20, 2023

Hi @Lucas Ferreira 

Yes you can do this using Automation - something like this should work:

  • Trigger: Field Value Changed
    • Field to Monitor = Components
  • Condition: Issue Fields Condition
    • Field = Issue Type
    • Condition = equals
    • Value = Story
  • Branch: Related Issues
    • Type = Sub-tasks
      • Branch-Action: Edit Issue
        • Field = Components
          • Value = Copy from Trigger Issue or Parent Issue

---

A few notes...

  • "Copy from" in the Action is available from the breadcrumbs menu (...) in line with the field's name. Select COPY, then you can choose where to copy from
  • You can limit the Trigger as needed for specific change types (value added or deleted), or for specific operations (eg. create issue) as needed
  • Be mindful of your Automation executions - Free plans only get 100 executions per month, so it might be beneficial to upgrade to a Standard or Premium plan. See details on execution limits on this help page

---

 Let us know what you think!

Ste

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events