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
Next: Root
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.
like scrum software to service desk : IT service desk
This is still a problem in 2022. Creating a new project doesn't work because you also cannot re-use the project key. Now this new project B will bother me and others who use it.
Hi @kalyan,
Yes, and the steps is as follows..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @George Dunlop@Agust Thorkelsson
Only system administrators can modify this configuration, project administrators cannot make this change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am a system administrator. Still no option. Also, JIRA keeps coming up with HTTP Status 500 – Internal Server Error errors today.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Ollie. But I'm the system administrator as well. That's why I don't understand why I don't get the option.
Or is SITE ADMIN not same as system administrator?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahh just noticed something. There's an inconsistency going on between project settings based on project template when you initially create the project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, this is the same for me. And it's the top one I'm trying to change project type for. With no option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I ended up starting from scratch creating a project using this link [yourdomain].atlassian.net/secure/ManageRapidViews.jspa which can also create projects with sample data (which is another inconsistency as the sample data cannot be found through the regular create board approach here [yourdomain].atlassian.net/secure/BrowseProjects.jspa). You'll also notice after choosing create a Scrum or Kanban board that you can choose "Board from an existing project". Maybe that would help port it across?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, Administrators can modify it in Project Details
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here's the instructions I found for next-gen cloud-based conversion of projects: https://support.atlassian.com/jira-cloud-administration/docs/convert-a-project-to-a-different-template-or-type/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Years later and the solution is still "make a new project and port the issues". We have guidelines for project and key names and if someone fat fingers the template type they can't delete the old project and make a new one with the same name and key, so now we have a bunch of names with `_2` or `_3` and keys ending in `B` and `C`.
If we can quickly and easily batch move issues, that mechanic can be used internally to change the project type without us doing that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.