I'm a big fan of Jira and have been using it for many years. I love the flexibility of the application and have setup many collaborative processes, from employee prospecting and onboarding to multi-tiered development projects across squads/tribes using various agile frameworks and pretty much all Atlassian install products.
Most recently I started at a new company which was using Jira Classic (cloud) with a couple of teams - soon we'll be spinning up more teams. I thought it might be advantageous to migrate the projects to Jira Next-Gen (the simplicity was appealing) and spent last week doing so with the newest team's project (4 sprints worth of tickets). It took time as I wanted all the Done stores and Epics in the one project. It was a somewhat onerous task - the epics lost links to associated stories along with the loss of Components, also you lose story points when migrating to story point estimates - so I basically had to replicate the components using Labels, then transition the stories an epic at a time, then re-associating each "no epic" story to a new Epic in the Next-Project. I did this by first migrating everything that was done in past sprints, then the current backlog, and finally the stories in the current sprint. It was tedious work but I was able to do so without impacting the team's velocity.
Now that I'm in the new project, I'm realizing that there's just too much missing (available in the classic version) to effectively use the Next-Gen project - the main problem is the ability to coordinate multiple squads in the same tribe pulling from a common backlog. I had planned to add people then split into two squads but there's no effective way to do so using the new boards (would need to be able to start multiple sprints from the same backlog, a feature that's missing). I also find the lack of workflow automation rather depressing. I need a rule that assigns a story back to the developer when it doesn't pass code review. The current rules only work progressing the tickets and not regressing. There are other gaps that make things much harder rather than making things easier (I'm a big fan of simplicity but the current app is perhaps a bit too MVP-ish).
It's rather depressing to know that I'll be spending another week moving all these stories back to the original project. In hindsight I would have copied everything into the new project rather than moving and I'd recommend that method over what I did (and yes when I created the project I worked through some sample tickets to see how things worked. As with anything it's the edge cases that kill you). In any case, I hope this feedback is useful and I hope that at some point there's an iteration of this product that's actually useful.
...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...
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