I have two team-managed spaces, in which tasks (work types) are moved from one to another in a weekly basis. When moving from one space to another, all fields should be preserved.
Currently I have a field created that is in use on both spaces, as image bellow:
This field is working as expected. When I move work from one space to another, the field information is preserved.
I want to create move fields to be used on both space, including of other types (like rich text), however I don´t recall how I setup it before.
What I have tried:
- when I create new fields in the admin settings, I could not add those fields to the spaces.
- when I create new fields in the space settings, those fields are local and could not be used in the other space.
This is driving me crazy...
Hello @Gabriel Marques
Welcome to the Atlassian community.
If you want a field that can be shared between Team-managed projects you must create it from the Jira Settings (gear icon next to your avatar) > Work Items > Fields screen.
The field needs to have a global context.
You can find more information about this in the original announcement published in 2022.
Announcing the ability to re-use global custom fields in team-managed projects
(Note some of the screen images may be a bit outdated since there have been quite a few UI changes since 2022.)
Hello @Trudy Claspill thank you very much for your help!
I guess I found the problem: it´s a bug!
Initially, when I had only those two team-managed spaces, no mather what I did the software did not allow me add the fields created by admin, it only allowed creation of local fields, that could not be shared with other spaces.
After extensive trial and error, I figured it out that after I created a new company-managed work space, now it allows me to add the fields created by admin:
Bellow the same page after I deleted the company-managed space, I am no longer able to add fields!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is interesting! I found that documented as a change request in Atlassian's public Jira instance. The CR was created just 12 hours ago:
https://jira.atlassian.com/browse/JRACLOUD-97974
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I usually use a Global Field configuration scheme that I add on to the project at the time of creation. I believe you can update that after the space/project is created.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am not sure what you mean, nor that this is available for a team-managed space.
Is Global Field only available for Jira Product Discovery spaces? I see such option for a space in Product discovery space (bellow), however not for the Team-managed space (previous message).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.