I have a simple, single select list custom field (with global issuetype availability).
I have given my custom field project level custom contexts . I can add these contexts easily for company-managed projects, but for a team-managed project, i am unable to set a custom context. I have tried this both as:
On the system level Custom Fields > Add Context setup, the project is missing from the available projects list
On the project settings > Issue types (Screen layout configuration) i can see my Custom Field, but when I select the ellipsis > I see here only a global context but there is no ability to " + ADD OPTION" for this project, it is greyed out
Can I really not share one global company managed field to allow it to span across the range of Company and Team managed projects that deliver this product and give each its own context?
Seems kinda odd to me... Is this a bug or by design?
Hi Averil - Welcome to the Atlassian Community!
That's correct - Team-managed projects are severely limited and intended to be used completely independent of ALL other projects. Though you can use some global custom fields, that functionality, too, is very limited and you cannot add custom context to them.
Ouchy! OK and thank you so much for the swift response - appreciated
I have a workaround to add the needed content to the available global default list so that users can select their option, but it isnt a very graceful solution. I have added a value of "Raise a request to have your teams context added" to try and steer future projects to find the same workaround for now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The best workaround is to never create Team-managed projects. ;-)
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.