You can edit the workflow scheme associated with that project and then have each workflow for each issue type.
Eg: Issue type Bug can have issue reporting workflow and Issue type Task can have Task assigning workflow for same project.
This is same for field configuration as well as screen scheme. You can have multiple for a project, each one associated with issue type.
Hope this helps
Whilst @Vasiliy Zverev is correct that you can use two workflows for different issue types. If you are meaning you want to have two different sets of column headings on your Agile board so that you can reflect different parts of your workflow process then this is also possible but it requires you to set up different boards for each part of the process. These will be based on the same project and show the same issues.
So for example if you have a workflow as follows
To Do - Triaged - Planned - In Progress - In Review - Awaiting Release - Resolved - Done
You might have one board with columns as follows for Planning
New To Do - Triaged
Underway In Progress - In Review - Awaiting Release
Done Resolved - Done
and a second board with the following mapping
Backlog To Do - Triaged - Planned
In Progress In Progress
Testing In Review
Release Awaiting Release
Resolved Resolved - Done
Or any other mapping that might be more appropriate to your business needs.
Hope this helps.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs