I was naive enough to set up my project using a "next gen" board-- as someone who is fairly new to Jira I simply chose the suggested option. As a gentile introduction to the software it is great, but it is just that. Any attempt to use the next gen boards for any sort of moderate or advanced use case is bound for failure.
Putting aside the confusing business practice of pushing customers to an inferior product for the same price. Lets talk about what happens when you realize that a "next gen" project doesn't fulfill your teams needs... You're out of luck-- no way to convert it to a classic board. The best you can do is move all your tasks to a new "classic" board (which from my experience is a hugely unintuitive and manual mapping process) and hope that everything transfers ok. If not, well you moved not copied, so your out of luck.
Even more, if you use the Jira API you'll have to completely re-write your stage change call (at least), because they are not compatible.
As far as I am concerned save yourself the pain and use the "classic" boards. "next gen" is a flashy waste of time that will cause you more issues than it solves. This can be clearly illustrated by the number of hits are returned when searching "Jira Next Gen to Classic" on Google.
As for people like myself who seemingly are stuck with their "next gen" boards. Atlassian, please implement a way to convert our boards to "classic". We need the functionality that is already implemented and was the default before. We are currently being robbed of value by having been directed to use the "next gen" boards.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events