I work for an organization that is only done scrum in Jira. I have gotten approval to build out a Kanban board. I've worked with my team to create a new set of status's, I've built a new workflow and workflow scheme and I'm ready to implement the new scheme.
Here is my question, would it be better for me to create a new project and associate the new workflow with the new project
OR
apply the new workflow scheme to the current project?
Here is my concern, what happens to the work items that are currently in a status that is not associated with the new workflows?
If I create a new project, I can include the old project in the board filter.
I'm open to suggestions and I'd love some discussion on the right way to do this. Thank you
Hi Buck,
Congrats on the move to Kanban!
If you simply move your existing project over to the new workflows, you will have to map the existing statuses that are not in the new workflow to a status that is. It's simply a part of the migration process when connecting a project to a new workflow scheme. The Backlog and Done ones (and probably others) will move with no need to map.
If you want to see the existing project issues in the new environment, then just go that route. It's really up to you - I wouldn't say there is a right or wrong way to do this one.
Thank you @John Funk I didn't know mapping would be a part of the new workflow scheme process. Great info.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is if you are moving current issues to the new workflow and they are in statuses that don't exist in thew new workflow scheme. As it moves them, it will prompt you for the mapping. :-)
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.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.