Hi all, I was going over this article as a way to help me, but I'm still stuck.
Simplified, is there a way to combine the "Create a New Story" step with the "Create sub-tasks" action? I would like to have my Sub-tasks actually be Stories, not sub-tasks, under the Epic when Summary contains a key word.
This is what I have so far:
Has anyone found a way to make this happen? Or at least define what you want your news stories to be if taking the route from the link above? Thanks.
Hello @Alex Senyo
Welcome to the Atlassian community.
I'm a little confused.
If you want to create Stories under your Epic then you need to use the Create Issue action.
Why are you using the Create Subtask action? That action will only create subtasks.
Hi Trudy, that's what I'm asking. Is there a way to use the subtask checklist and apply it to the Create Issue action?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can't use the Create Subtask action to create other types of issues. It can be used only to create subtasks.
If you want to create a Story under the Epic you must use the Create Issue action.
Perhaps I am misunderstanding your question. Are you asking about creating a story under your epic and then creating subtasks under the newly created story?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No you're good, and it's just my frustration with this program and why you can do A,B, and C with some things but not for others.
So what's the best way to create pre-titled Stories automatically under a created Epic? I have those 11 issues that I want to be added to every "Launch" epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe the only solution is to use 11 Create Issue actions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good afternoon @Alex Senyo .
So you would start off your rule creation the same way you have but then you will create an issue type and select story, you will have to do it 11 times.
Then to tie it back to your epic you will need to make sure for each story to add the parent field as a field to set under the drop down. If you don't do this you will just create stories that are not connected to your epic.
Once you have added that field to each story you are creating you will need to make sure the parent is assigned as the trigger issue that started your automation rule off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.