How to create an issue with a specific workflow assigned upon creation?

[Samuel Atkins]

I have a JIRA project that contains multiple pre-existing workflows. I want to create a new issue type in this project but not have the project default workflow automatically assigned to it on creation, but instead select one of the other workflows already in use in the project at creation. This way I would not have to do all the extra work of re-assigning a different workflow to the new issue along with re-assigning statuses from the previous workflow when I change out the default workflow for the one I really want for this issue. Can this be done?

Thx!

S>

[Mark Segall]

Hi @Samuel Atkins - To make sure I understand correctly, are you asking:

1. Whether it's possible to have an issue type assigned a specific workflow
   1. Is so, Yes.  You would need to update the workflow scheme issue type assignment to the desired workflow
2. Whether it's possible to change a workflow on an issue by issue basis for the same issue type
   1. No - issue types are bound by the workflow scheme as to which workflow they will be assigned.  However, it is possible to get creative with workflow conditions

I hope this answers your question.

[Samuel Atkins]

Hi there, and thanks for your clarification questions. In essence however, no neither of your questions are what I'm asking. My question is, when I am in the process of creating a new issue type, can I assign a specific pre-existing (and not the default) workflow to the new issue type as I'm creating it? And if so how because I do not see where this can be selected? 

Currently what happens is it assigns the project default workflow and then I have to go back and re-work everything related to the workflow assignment and this is a big waste of time.

Any suggestions? And thanks.

[Mark Segall]

Hi @Samuel Atkins

Not as you're creating the issue type.  It would be a series of steps and those steps depend upon whether you're working with Company vs Team managed projects:

Company-Managed Project

*Note - Jira Admin rights are required

1. Create the issue type
2. Add the issue type to the project's Issue Type Scheme

   1. https://YOURINSTANCE.atlassian.net/plugins/servlet/project-config/YOURPROJECTKEY/issuetypes

3. Navigate to the project workflow scheme
   

   1. https://YOURINSTANCE.atlassian.net/plugins/servlet/project-config/YOURPROJECTKEY/workflows

4. Click Add Workflow >> Add Existing
5. Select the desired workflow from the list and assign it to your new issue type

Team-Managed Project

*Note - There are no global workflows in team-managed projects.  Each one is created with a default flow and you have to update accordingly.

1. Create your new issue

   1. https://YOURINSTANCE.atlassian.net/jira/software/projects/YOURPROJECTKEY/settings/issuetypes

2. Click Edit Workflow and adjust accordingly

Hope this helps.

[Samuel Atkins]

Thanks Mark,

Yeah that's what I thought. That's the correct methodology as I understand it ( I am an Admin) and there is no way to avoid having to re-associate the desired workflow in place of the default. In this process you also have to remap unwanted/un-needed statuses from the default workflow as well when you replace it with the new one, which is a hassle and would be much simpler if you could just assign the workflow you desired from the get go. Anyway, it is what it is right.

Thanks again.