I have a custom field that has dropdown options that I need to add to... for some reason, the field is locked suddenly and I cannot add any additional options. It also says when I edit, that the field cannot be used as it I have a message that the context has been removed. How do I dig out of this as I rely upon this field in my service management project.
Welcome to the community.
If this field is a custom field in a Team Managed project, contact Atlassian support to assist with this Warning message to allow you to continue editing the field.
If it is not a field from a Team Managed project, can you show a screenshot?
Fields with a lock icon are system fields or fields from a 3rd party app (that the vendor doesn't allow to change).
If you get a message a context has been removed, then the options that where in the context are gone
The name of the field is named Work Category and it is a custom field I created.
Oddly, when I try to edit the list in the Fields area, I cannot, but when I attempted within a Request Type, the original checkbox list was empty (I originally had about 10 options there) - but it let me add options there and they did save.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did you create this field in a Team Managed project or from the fields option in the Work items section in Jira Administration.
If it's the 1st, the field can be seen in the Fields section, but not edited, then you need to be in the Team Managed project and adjust the field there.
As this field is made in the project and only available in that project.
Please accept my answer as a solution, if my answer helped to solve or provide a workaround to your request.
This will help other community member trying to solve the same or provide them with a work around
P.S. If the answer is very valuable to you, please share some kudos.
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.
Hi @Christine Sbatella , what is the name of this field? I expect this is a system field which cannot be edited.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Work Category - while it says it is not in any project, it most certainly is AND is used in every request type
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is interesting. There is a Work category system field. Did you create this custom field for CMP or TMP project(s).? The interesting part is that your screenshot does not indicate system field like is the case for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This was created in a Team Managed project.. Ironically, I don't see any other Work Category fields - perhaps creating one with the same name used in different type of project caused the conflict?
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.