nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Team Managed Projects - Can't edit a custom field's context to Global

Andy Rouse_2mjjro

We have an existing Team Managed Project and have recently created a new one.

I know that it's possible to create custom fields with a global context, but I'd like to add some of the existing fields from the existing Team Managed Project (so that we can "Promote" tickets from the new project to the existing one occassionally)

On the new Team Managed Project, I've managed to create new custom fields and give them a global context. However, on the existing project, I can find no way to upgrade the existing fields.

They don't turn up in the "Custom Fields" management screen and I can't see a way to edit their properties directly.

Is this possible? Or do I need to create new global custom fields, then migrate the existing custom fields to those?

Accepted answers

Trudy P Claspill

Hello @Andy Rouse

You cannot "upgrade" a custom field created within a Team Managed project to be a globally managed Custom Field (appearing in Jira Admin Settings > Issues > Custom Fields).

You do need to make new global Custom Fields and use those to replace the locally defined custom fields in the Team Managed project.

All comments

Trudy P Claspill

Hello @Andy Rouse

You cannot "upgrade" a custom field created within a Team Managed project to be a globally managed Custom Field (appearing in Jira Admin Settings > Issues > Custom Fields).

You do need to make new global Custom Fields and use those to replace the locally defined custom fields in the Team Managed project.

Andy Rouse_2mjjro

Thanks @Trudy P Claspill - I have created the new fields, but since discovered that any attempt to update Team Managed project tickets with the CSV Upload tool provided by Atlassian will result in the Epic being cleared from the tickets (It's a known bug/feature).

Unfortunately, this has reduced the usefulness of the new fields, as we cannot migrate to them!

However, thank you for your accurate response.

Trudy P Claspill

You could use an Automation Rule to move data from one field to another without impacting the link between Epics and their children.

Andy Rouse_2mjjro

@Trudy P Claspill - Interesting, thank you. When would that rule be triggered?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

cloud

jira-software

jira-software-cloud

team-managed-projects