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
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
Hi Atlassian Community, I am Hiroshi Fukai, this is the first time to post. Nice to contact you.
I have a question, I am encountering that I am unable to add a field to a request form, even though the field configuration, screen scheme, and issue screen scheme are all configured. For example, in the case below, "Approver 3" could be added, but "Approver 1" could not. What is the difference? Please advise. Thank you very much.
Welcome to the community.
By the looks of it both fields are custom user fields. These fields are supported by the forms option in JSM.
If this is correct, but you are unable to add the field you could delete the CF and crate a new one and see if this works, if not then it suggest to raise a support request at Atlassian.
The support department has access to the backend of your instance and can see logging, they might see a reason for the issue you experience.
Thanks for the answer. Finally, I found the solution that missing context of the CFs was the root cause. When I associated the target project with the context configuration of the CFs, I could add them to the request form.
Issues > Custom fields > Context: