Hi folks,
I’d like to ask how to build a Jira automation that allows users to choose the issue type when creating a ticket. The expected user flow would be:
Trigger the automation
Select Create a ticket
See a dropdown to choose the issue type (Story / Task / Sub-task / Bug)
Confirm the selection
Successfully create the assigned ticket
Thank you.
Hello @Sandy Hsieh
I have questions about your scenario.
What decisions does the user need to make?
Are any of these decisions static and able to be determined by the first item that you create? For instance, when you create a task you always want to create three subtasks and assign them respectively to Bob, Joe, and Sarah.
The possible solutions through automation depend on what information is known and static every time versus what information would have to be supplied by the user.
It is possible to have an Automation triggered by the creation of an item to automatically create child items, but the answers to all the questions must already be known and available programmatically to the automation, for instance available from fields in the created issue or simply static values like always creating three child items. That type of rule trigger doesn't support getting information in real time from the user.
Alternately an Automation rule can be triggered manually by the user. In this case the rule can be set up to prompt the user for some information, and then executes based on the information provided.
Hi @Sandy Hsieh
This can't be done.
Automation tiggers act on existing work items or when work items are created.
There is no option to trigger an automation from scratch.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marc, Nicola and John
Thank you for the suggestion, and apologies—I missed an important point earlier.
The main reason I want to create this automation is that I usually start by creating a main ticket (such as an Epic, Story, or Task) with detailed information in the description. I then need to create two to three child work items or sub-tasks and assign them to different people. Ideally, when creating these child items, I’d like the content from the main ticket’s description to be automatically carried over, so I don’t have to repeatedly copy and paste the same information.
That’s why I’m hoping to build an automation that helps create child work items or sub-tasks while allowing me to choose the issue type (Story / Task / Sub-task) during creation.
Hope it's clear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sandy Hsieh
So you can create a rule, based on work item created trigger, check if the created type is Story, then add an action to create sub-tasks in the story.
You can also create a same rule based on Epic that is created, that a Story is created.
If you then want the sub-tasks to be created, make sur the rule action on creating the story has the checkbox enabled for the option "This rule can be triggered by another rule"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Sandy Hsieh
All users that are in your Jira space will be able to select any issue type - this is a system field. No automation rules are needed. If you need to increase the security so only certain users can see certain work item types, you would need to include the work item security.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sandy,
Why not just have them click on the blue Create button and just create a work item?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, that's completely different from your original question. Yes, that is easy to do with a Work Item Created trigger.
Then add any conditions needed.
Then add an Action for Create Work Item under that. Select the fields you want to copy down. Click on the 3 dots beside each field and select Copy.
Then choose From Trigger.
Be sure to add the Parent field and select Trigger Work Item.
Unless there is something else, that should do it.
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.