You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Can someone confirm my suspicion about this: The choices in a custom field created with type of "select list (single choice)" or "select list (multiple choice)" CANNOT be updated/added to once the field is created?
If it can be done can someone please tell me how because I'm not finding a way to do it. I'm on JSM Cloud.
If it cannot be done I really want to know why Atlassian can't let us do this with a custom field.
Trying to find documentation on this hasn't been easy.
Hi @Lisa T_
I'm not sure what you mean, if you click on the 3 dots option next to your field (custom field administration) you will have an option called "Contexts and default values", there you can edit the field options you already have and add new ones if you need to.
https://support.atlassian.com/jira-cloud-administration/docs/edit-a-custom-fields-options/
Maybe I'm missing something.
Regards
@Charlie _DEISER_Thanks for your reply! I guess that's it. Unfortunately I wouldn't have though editing a field's selection list would be under "Contexts and default values" but under "Edit field". I don't find that an intuitive choice.
Thanks for the link also. I don't know what search phrase you used to search the documentation, but even a search with "custom field" showed that page almost near the bottom... I didn't scroll that far down :-)
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad I was able to help. I agree, it's not intuitive ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, it's a historical thing though - "edit field" refers to editing a field "header" - the thing that hooks it into Jira projects and issue types.
Different types of fields have different configuration settings, including contexts, so they needed another name for them.
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.