Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Changing Project Type from Service Desk to Software?

Hi all,

As my team is moving from Jira Server to a newer product, I'm looking to change my project type from a Service Desk project to a Software Project. I've read here and there that this can't be done, but I assume that is in Cloud as I can see I have the option to in settings?

I'm wondering if anybody has done this before - are there are any risks /issues associated with doing this? Of course I expect the Portal to break, and SLA information to vanish from tickets, but outside of that, is there anything I should look out for? Additionally, will this have any impact on my future move to Cloud/DC?

Here are some things I plan to test before going through with this in prod:

  • Workflows (make sure everything goes through okay)
  • Custom Fields
  • Dashboards
  • Kanban Boards
  • Epic Links + Issue Links in general

Let me know what you all think.


1 answer

0 votes
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 08, 2021

Hi Luke,


Things you should look out for is permissions, notification, and e-mail setup. The permission and notification will significantly be different. Also, e-mail processing will need to be done through the Jira mail handler instead.

Doing clean up like this is better for the cloud. Putting projects where they should be and maintaining the instance is part of the formula in getting to the cloud smoother.

DC is more easier.

If you want to make sure expectation are set to the exact way you want, you can create a software project to the exact specifications and just bulk move the issues over if it's not a whole lot issues to move over. Not a whole lot meaning less than 1k.



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events