Forced to migrate to company managed project

Question

Hello,

Until recently I was able to create and update custom fields in my team-managed project by programming them in the app I am developing with API requests.

I now learned that it will only be possible to create and edit custom fields with the custom UI module in company-managed projects, and not team managed projects.

This means I will be forced to create a new project, migrate all my information to there and now recreate any custom fields that were created through the new-gen option (and replace their new fields in my code).

That will be countless hours of work to overcome the change in the settings.

Is there any solution for easily recreating the new-gen fields in a migrated project (from team to company)?

I have read the documentation page on migrating and did not find a solution: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/.

Many thanks,

Talia

Ka Sidro1 · Answer

Thank you

Nic Brough -Adaptavist- · Answer

Fields in TMPs only exist in that project.   So if you want to report the same thing from more than one project, you end up with a mess.

If, for example, you have "start date" and you add it to 3 different TMPs, then a simple report of "show me start dates for issues in the projects" will come out with a table like

Issue  Start dateStart date Start date  ABC-1123  16/3/2023   ABC-456  18/4/2023   DEF-128  12/6/2023   GHI-12   16/1/2023

Ka Sidro1 · Answer

Thank you for your reply!

It does work now, I'm not sure what if I did something different or if it was just a hiccup in the program, but I was able to create and update the field in my regular team managed project.

Can you explain that last part about not being shared nor reported?