I want restrict editing of field in team managed project

[Rasajna Meka]

I want restrict editing of field in team managed project, only certain group has to edit it

[Dave Mathijs]

Hi @Rasajna Meka , to my knowledge, this is not possible for team-managed projects as the fields and issue layout are linked to the Issue types in the Project settings. There are no operation issue screens (create/edit/view issue screen) in team-managed projects.

[Rasajna Meka]

Thank you @Dave Mathijs  any other workarounds possible like automation

[Dave Mathijs]

Don't think so, another reason why I never use or advise to use team-managed projects. So, a workaround would be to convert it into a company-managed project.

[Rasajna Meka]

I thought of of converting to company managed project, but there were lot difficulties in converting as I have to create a new project and Move issues , is there any way to deal with it

[Dave Mathijs]

There is no other way around I'm afraid.

[Rasajna Meka]

any known issues you figured out while you migrated/moved team managed to company managed project

[Hamza Chundrigar]

Hi @Rasajna Meka 

I would suggest reading this article if you're considering migrating your team-managed project over to a company-managed project:

• https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

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's 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 to 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 to the custom field used in team-managed projects (Story point estimate).