You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have aproblem using JIRA automation capability. I want to create a rule so that when we create a new issue it automatically create the story from it and in that story it created the predefined subtasks.
I could create this rule so that when I create an issue in JIRA and put in the summary for this issue manaually, the issue is created. However, wehn I trigger the rule that was created before, it creates a new story but it adds the subtasks that were part of the rule I created to the manual issue that I create. So what happens on the Backlog, I get two stories: one without subtask created when I trigger the action and the other that was manually created by me which holds all the subtasks!
How I can define the automation rule so that only 1 story being created with all relevant subtasks when I trigger the action?!
Thank you for your help
You must add at least one component (see yellow marking below) in the branch to get rid of that info. Like this:
All subtasks you want in the new Story should be located in that new branch. You can drag-and-drop them into that branch if they still exist in the main "thread".
Hi @Tim Kopperud ,
Sorry for my late reply as I was so busy recently!
Unfortunately the solution you proposed doesn't work meaning still it created a new story but put subtasks under same story which was created using create a new issue. So, basically I see two stories, one automatically triggerred when I call it from actions menu and second one which was manually created by me
What do you think is the root cause?
You rule branches to Current issue, not All created issues. Se my image in the orginial answer.
Current issue is always the issue that "flows" into the rule when it starts, and it will be that way during the whole rule execution. You therefore need to change the issue context away from current issue into the newly issue created.
Yes, you can delete the issue from automation.
If the original issue uses the same workflow as your Epic I might suggest you instead change the issue type using the Edit issue action. You don't need to create a new issue for this. Then you will keep all relevant history, even that it was nad when it was converted to Epic. But it's based on your exact needs, if want to "have a fresh start" on the Epic or if you want to keep the history data.