Change default issue type in new UI

[Deleted user]

I created a new project recently and it has a totally different project UI than the other project my company has been using for 1.5 years.

In this new UI, I can't figure out how to change the default issue type for newly created issues. Help!

All the support documentation I've found online is for the old UI.

[Hamza Chundrigar]

Hi @[deleted] 

Welcome to the Atlassian community.

Based on the screenshot you provided in response to Nicolas’s comments, I can see that you’re using a team-managed project.

Please be advised that you are unable to define/set a default issue type for team-managed projects (atleast as of today). Being able to define and set a default issue type is a functionality that is only available for Company-managed projects.

There is a feature suggestion open for team-managed projects though. Please feel free to add yourself as a watcher and/or vote on the feature request:

• https://jira.atlassian.com/browse/JSWCLOUD-17743
  
  

Best,

Hamza

[Deleted user]

What an odd setup, if it is "team managed" I can't do a simple thing like change the default issue type. I didn't even intentionally create a "team managed" project! Can that be changed now?

[Hamza Chundrigar]

Yes, you can migrate all of your issues from a team-managed project to a company-managed project. If that's something you're interested in doing, then you'd need to create a new company-managed project to receive your existing team-managed project issues.

You could then follow the steps listed in this Atlassian Knowledge Article that walks you through how to migrate all over TMP issues to the company-managed project.

---

The information below is listed at the bottom of the Atlassian KB article but I've mentioned it below as well for your consideration/reference.

Things to keep in mind if you migrate from team-managed to company-managed

Team-managed projects and company-managed projects are technically quite different. Here are a few things to consider when you migrate from a team-managed software project to a company-managed software project:

• Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.

• Custom fields: If you use custom fields in your team-managed project, a Jira admin needs to recreate the fields and add them to screen schemes and field configurations in your company-managed project. Custom field data will need to be recreated, otherwise, it will be lost.

• Issue types: If you added your own issue types to your team-managed project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate with your new company-managed project. Learn more.

• Project access: Access to company-managed projects is controlled by a permissions scheme. Only your Jira admin can update your company-managed project's permission scheme. Learn more.

• Project and issue keys: Jira will automatically update the issue keys of migrated issues to reflect their new project. Any existing links to old issue keys will be automatically redirected.

• Reports: Reports data won't be saved. Even though your issues will be retained, data for your project's Velocity and Burnup reports won't transfer over and will be lost.

• Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed projects (Story points) is different from the custom field used in team-managed projects (Story point estimate).