Can I edit the issue details view on my board in a team managed project?

[Deleted user]

Usually when I click on the three dots and see the Board Settings option, I can click on Issue Details View and update the information that users can see on the Kanban board. 

However, on my current board (for which I'm an administrator of the board and project and overall jira account) I can't see that option. 

Is it because its a Team Managed Project and I just need to migrate it to a Company Managed Project? Can that be undone? What problems might that cause me- will be workflow remain valid?

[Tim Perrault]

Yes you will most likely need to change to a company managed project. Team managed projects have fewer options for configuration by design.

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).