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; } } }

Is it possible to use custom context fields on multiple projects? If yes how?

Paulo Cudjo

On our triage project board, besides the standard label field, we use a field called 'client(s)'. When moving tickets from one project to the other, we however lose this field and its values. We did already add this custom field to other projects as well, however it looks like it is threated as a new field, so when moved, it remains empty.

Is it possible to use a custom field and enable it on multiple boards? So that this info stays visible? Like how it works with the standard field 'label'.

Thanks in advance!

Accepted answers

Trudy P Claspill

Hello @Paulo Cudjo

Welcome to the community.

Are the projects in this case Team Managed projects or Company Managed projects? It will say at the bottom of the navigation pane on the left.

John Funk

Hi Paulo - Welcome to the Atlassian Community!

Make sure that the context for the field includes the new project.

All comments

Trudy P Claspill

Hello @Paulo Cudjo

Welcome to the community.

Are the projects in this case Team Managed projects or Company Managed projects? It will say at the bottom of the navigation pane on the left.

John Funk

Hi Paulo - Welcome to the Atlassian Community!

Make sure that the context for the field includes the new project.

Paulo Cudjo

Thanks for your reply! We are using both team managed and company managed projects

Paulo Cudjo

Good point! I noticed that as well but could not seem to add/remove a project from this list. I guess that has to do with having the right privilege's?

John Funk

You would need to ba a Jira Administrator to make the changes.

Paulo Cudjo

Thanks a lot!

Trudy P Claspill

Team Managed projects by design do not share custom fields with any other projects. Even if two Team Managed projects have a custom field that is identically named, on the back end Jira considers those to be two different custom fields.

Use of the custom field configuration options and context available through the Settings > Issues > Fields options available to a Jira Admin will be relevant only for Company Managed projects.

Because the field is considered a different field in each Team Managed project, and a different field between Team Managed and Company Managed projects, if you try to move an issue between Team Managed projects or between a Team Managed project and a Company Managed project the data will be lost. The only move where the data can be preserved is between Company Managed projects.

Paulo Cudjo

Appreciate the elaborate explanation Trudy! Makes a lot of sense and I learned something new today

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud