Switching from Classic to a more "modern" workflow

[Paul Miller]

We used to use Mantis and are migrating to JIRA for everything. We are currently using the "Classic JIRA Workflow" which more closely matches how we worked in Mantis. So an issue goes from Open to Resolved to either back to Open or Closed if it's truly done.

However, I'd like to start using more modern tools for scheduling work, such as the Backlog and SCRUM board, and the Classic JIRA Workflow scheme does not work with that.

Can anyone suggest a better scheme for what I want to do that will also let me use the other nifty tools that are in there? I also need a bit of hand-holding on the proper way to switch the project's scheme to the different one.

Many thanks!

[Warren]

Hi Paul

I think the other point to note here is that you should decide what process (workflow) you currently have, and then make Jira match it, as opposed to seeing what is in Jira and bending your processes to suit.

[Nic Brough -Adaptavist-]

If you create a new Scrum or Kanban project, they will give you another style of workflow as a default.  You can then use those workflows in your existing project.  Although I tend to use them as a starting point, rather than a workflow that matches.

Although, the classic scheme does work with backlog and scrum, if you adjust it a bit and map the columns to the workflow.

[Paul Miller]

Thanks Nic & Warren for your replies. For some reason I didn't get any notification when you replied, so sorry for the delay.

I did manage to get it working as Nic suggested, by finding the columns page and mapping the columns over - then the backlog started working.