You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're looking to simplify Jira and we need your insights to help us.
The Jira platform lets software teams, service teams, and business teams collaborate with a single site to track their work.
We sometimes see teams change their project type after setting up a new project - usually from a software project to a business project.
Have you ever changed a project's type? If you have, why?
@Nic Brough -Adaptavist- Thanks for the insight.
From my observation when moving to another project type there are a few parts of the project that don't work correctly as the specific product features have not been configured by default (example: moving to Jira Service Desk there would be no queues, moving to Jira Software there would not be a board). Do you find that there is a lot of configuration needed to make the projects work after changing the project type? Why not move the issues to a new project?
I'd judge each case on its own merits - we often did move issues to new projects.
You still have to do all the "new" config whether you're moving or flipping the flag. Moving to a new project can mean having to replicate some or all of the current config of the old project too (the further away from the template you use, the more needs doing), and that can become long and boring if you've done things like project-specific custom fields. So we always look at how the projects currently work and how we want them to, then decide which way to go from there. Generally, the starting point is "just how much do you want to change in this project?"
This new restriction (no longer able to change project type) has inadvertently hindered my organization ability to support projects. We have some projects that were setup as Business projects that would now like Boards setup and are unable to meet specific requirements without converting to a Software project.
It is a problem to setup a new project with a new key due to the business impacts (teams are already referencing existing key).
Are there any work arounds to avoid a new project setup? This would be be greatly appreciated. At the time of setup we have previously witnessed changes back and forth between Software and Business projects so this was not considered a critical decision at that time.
Unfortunately, there is no workaround that gets you 100% of what you're looking for. One of these two options might be an alternative.
1. New project option
Unfortunately, during the move; the issue keys are not guaranteed to maintain the same issue number (unless you move one issue at a time to match up the sequence, watch out for deleted issues). Example: OLDKEY-1 could become NEWKEY-2
2. Board only option