I think there's a good chance we all have development backgrounds.  It shouldn't be about ROI, it should be about customer satisfaction.  Also, if the answer is no, they should at least tell people why instead of leaving everyone here hanging forever. 

Coming from a Development background, what we are asking could be very difficult to accomplish, maybe the ROI just isn't there. Perhaps that is why no one has answered this thread. Has anyone tried communicating with them directly?

Not sure what happened with my last comment–but:

@Andrew while I agree with you on tone, it's absolutely infuriating to be essentially ignored on such a reasonable and oft-requested feature.  There currently doesn't appear to be a solution to the issue without spending days of work and losing all history in the process–if there is I think a lot of people here are missing it.  Perhaps SOME communication from the development or product teams would be helpful since this issue has been open for over half a decade?

Munjal, all I am saying is complaining about it isn't the way to go. I'd appreciate it if you could keep that kind of commenting off this thread

Andrew - for the past 4 years??

I don't believe that it's the devs issue - it's the program manager / product owner issue.

@Munjal

That is a very unfair and unprofessional response. I am certain the developers care for their users and are working their hardest.

Hey guys! What's wrong with y'all?

It's been more than 4 years that this feature has been asked and y'all not taking a serious look at this?!!

Or is that you don't give a shit about y'all users?

+1 I will also like to see this feature added. Project teams can change approach and adapt midway.

Thanks everyone for their input. We are actively working on making the transition between Scrum and Kanban seamless.

+1 please add this... My client has a kanban project/board and is moving towards needing more forward planning... thx, JP

+1, please add this missing functionality. Current method of replacing a Kanban board with a Scrum board of the same name via board deletion or vice versa is rather unintuitive.

I get this question almost daily from the teams that use the Jira instance I am an admin for. It's very frustrating to not be able to do this and causes a large amount of extra work. I would love to see this feature added

Lots of people are looking for this feature according to the related article: https://community.atlassian.com/t5/Jira-questions/Change-Board-Type-from-KanBan-to-Scrum/qaq-p/82343

I for one would also like to see this feature. As project structures and teams change and adapt so do the way things are done. Personally the division of Kaban and Scrum boards doesn't make sense to me. The categorization of these two types does, but dividing them into separate buckets entirely does not.

This feature would be helpful.

I have many users who have created complicated quickfilters and swimlanes based on JQL and having an easy way for them to switch or "copy and change board type" would be most helpful.

I just clicked on my Kanban board, clicked the options (...) icon, clicked "Create board", and added a scrum board.  Everything not done appears in the backlog, which is exactly what I wanted.  So it looks like this might actually be solved? You have to make sure you're viewing the scrum board in the dropdown, but it looks like conversion works in this way?

The proposed solution of exporting/importing board settings would do the work for me as well

Hope this is helpfull, it was for me.

In JIRA boards are simply views on projects. It is the projects that contain the stories, epics and other issue types.

This means that you can create a new board that points at an existing project.

Say for example your original Kanban board was called 'Team X'. When that was created it would have created a project called 'Team X' as well. The board would be a view on this project.

You can now create a new board of type Scrum. Make sure that when you create it you chose the option 'Board from an existing project'. Then select the project that you were using previously (in my example it is the one called 'Team X').

Now you have a Scrum board that shows all the issues that were on your Kanban board.

You don't even need to get rid of the Kanban board. Both of them will still work.

This is the Atlassian page that explains how to create a new board

https://pm.stackexchange.com/questions/17809/how-do-i-convert-a-jira-kanban-board-to-a-scrum-board

Recently i've looked at the rapidview table and see a column SPRINTS_ENABLED:

SELECT * FROM ao_60db71_rapidview;

It seems that a simple change of the value to 0 (Kanban) or 1 (Scrum) change the board type..

As an add-on, it would be perfect if we were able to choose which settings to import. So, if we already have an existing board, but want to import for example only card colours from another (template) board, then we'd be able to do that without overwriting any of the other settings.

salem.korayem160032443, that would absolutely work for me. I think it's an excellent suggestion.

Maybe a better solution would be "export/import" `board settings` that typically covers the following:

• quick filters
• swimlanes
• card layout
• card colors
• working days
• issue detail view
• estimation

mjopson yes, while you can create another board with the same filter, you will have to reconfigure all the board settings.

We use a lot of JQL quick filters and custom card colour configurations, and it takes a lot of time to reconfigure all of these, just in order to change the board type!

BR
Max

Thanks for watching and commenting on this Suggestion.

Where possible please add use-cases for the conversion from Scrum to Kanban or vice-versa, this assists with our research and potential solutions.

Please also note, as a workaround, it is fairly easy to create a new board which use the same filter, so a Kanban board can be created with the same content as a Scrum one.

Kind regards,
Martin
JIRA Software

+1 
It's important for us too - we have a huge kanban board for customer projects and now we need to move to a scrum oriented process on this board. This means I need to create a new board plus hundreds of tickets that need to be bulk edited.... 

1+. We could use that, too

Got the same concern, is there anyway we can switch from Kanban to Scrum view?

+1

Our project started with kanban, but now we want to switch to scrum with existing hundred tickets there so that we can have sprint.

Yes I would love this aswell. Please!

In my case, I do not wish to create a new board and have to update all my external links.

+2

++1

+1

Another big reason for a convert vs. "create new and replace" is to retain the URL of the original board.  Otherwise, you have to update Confluence links and make sure everyone stops using the old board and starts using the new board.  By converting the board and retaining the URL, these issues go away.

The original feature request description says: "The ability to convert Agile boards between Scrum and Kanban types."

Charle's suggestion is: "Create new Scrum board using same filter as an existing Kanban board".

Note that the difference is that the feature request is to be able to convert an existing Kanban board to a Scrum board, whereas Charle's suggestion is to create a new board not convert an existing board. The value of being able to convert is described in some of the above comments, such as the one from Tim Harris.

+1 for this!

+1 for Charles, just did this! Perfect.

I agree Charles: you can create a new board as Scrum with option from existing project. Then, wizard will ask for name and feeder project and you will get sprints management at all. Then you can tune up more board's properties: columns, filters, colors...

+1 this would be great for us. I'm sure others have experienced the need to migrate to other agile methodologies as they mature or as project teams are split to do R&D / enhancements vs maintenance etc.

Hi Charles - how did you get the backlog to exist for both? Would love to do that for my project. Thanks.

I'm a bit confused by this request. I had a project with a Kanban board, and when we changed to Agile I created a Scrum board for the project. The same backlog exists in both, so now I can switch between them at the click of a mouse. What am I missing?

I agree with the others - really need the ability to switch from a Scrum Board to a Kanban board and vice versa. Thanks.

+1 This would be a great feature. In the moment I've got a Scrum project and would like to use it now as a Kanban board, but it's not possible and I don't know what to do now.

Agree with majority of the above. This offers very little flexibility to project managers - this means that you have to perfectly plan from day 1 (and we are not perfect), there is no room to adjust course without starting over...Ouch!

+1 – I am dumbfounded that such important feature is missing. At different software development cycle, a different methodology is more appropriate for the project. There are legitimate reason to switch from Kanban -> Scrum and vice versa.

+2

+1. Such poor flexibility for a product ( whos 'support' ) uses words like - its "just a.." well, if it was just a board or whatever, why not support changing. Such poor use interface.

This feature would be extremely helpful!

please add this feature

+1 please add this feature

+1

Please add this feature!

Switching from Scrum to Kanban and vice-versa would be very useful to our company. We have a large number of supported products, and at any given time some are in active development and some are 'on the back burner' though still receiving some development and bug fixing. We use scrum for the high priority active projects and kanban for the low priority/maintenance projects. A given product can switch back and forth between methods repeatedly.

From my perspective, I use some outsourcing guys to code up. This is great but they use trello as their management interface. I can easily import from trello to Jira but it imports as a kanban and we internally use Agile/scrum so this, for me would save alot of work.

Thanks

Use case:

As a project owner, I create a project and start building out a backlog of tasks, and maybe developers even start working on some tasks. But woops, I just noticed I accidentally created the project as Scrum rather than Kanban, and I don't even remember why (not that it matters). Now I want to fix it since the project dev style is not using time-boxed sprints.

marion.rosner, we cannot provide any guidance at this time as to when, or if, we'll be implementing this Suggestion.
Please add your use-case or any additional details for the Suggestion so we can get a better idea of the need for it.

Regards,
Martin
JIRA Agile

Can someone from Atlassian please update on this? It was opened over two years ago. It would be good to know what the current status is. Thanks!

I second this. A lot of times project managers have card colors based on queries, quick filters, etc. which they used some time getting just right. Then they want to convert to another board type and have to redo everything all over. So a possibility to simply convert one board type to another would be a big help.

So a simple selection of board type on the configure board view, which would enable the plan mode when moving from KanBan to Scrum, remove the Release action from the work board, get rid of the sub-filter, etc.

Obviously there will always be some effort needed by the project manager if he switches board types, but the enabling/disabling of board type specific functionality would go a long way.

Alternatively, a way to template boards could be re-used in this scenario and possibly open up for much more.

We have requests from project managers all the time asking for a way to convert from Scrum to Kanban or visaversa.