jira 7.1 upgrade changed project type

[David Lunsford [Agency Consulting Group]]

Before executing JIRA 7.1 upgrade, we had many projects as "JIRA Defaults" and "JIRA Agile" blueprints with Service Desk components. After the upgrade, many of those projects that were classified as "Software" types have not lost their Service Desk component. How do we recover these? Are these settings stored in the DB someplace and automatically restored after changing the project type to Service Desk? Can you have a JIRA project type set to "Software" and add the "Service Desk" component as before with JIRA 6.4.7?

Urgent/major issue at the moment as hundreds of project under our large "landlord-tenant" design are impacted.

[Phill Fox]

I hope you identified this in your test instance first so you should be fine to go ahead and make your proposed change to see if it resolves this issue.

If this change does not resolve your issue you can postpone your plans for production upgrade and raise a support request to Atlassian.

If however, you have already run the upgrade on your production instance you should contact Atlassian support straight away for their help as rollbacks are complex and any elapsed time adds to the complexity.

[David Lunsford [Agency Consulting Group]]

The Service Desk information is retained in the respective tables for the Service Desk component. However, the other major issue is respective Project Admins have the ability to change the Project Type. This could be a problem if a JIRA project has many users defined in the Project Admin Role and one decides to change the Project Type from "Service Desk" to "Software" which removes the Service Desk Portal. If customers are using this portal to submit Bugs this could be an issue. So, providing a Large "Landlord-tenant" environment this ability to change the Project Type needs to be restricted to Global JIRA project Admins ONLY!!!

https://jira.atlassian.com/browse/JRA-60372