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
Welcome to the community. I agreed with @Nic Brough -Adaptavist- stated. Another thing that you need to ensure is that the new field must already been added in your project's screen configuration scheme.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
This is a team-managed project, so I have no feasibility on project screens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Team-managed project fields are independent of the global custom fields. Due to this, you will need to create the same custom fields again in the team managed project. Any system level (custom fields for company managed projects are not available for Team Managed projects)
There is an existing enhancement case with Atlassian to address this issue - https://jira.atlassian.com/browse/JSWCLOUD-20905
Hope this helps. If helped, please remember to click on Accept answer when you have a chance.
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the Atlassian Community!
That error is usually a transiient server-side error. Give it a few minutes and try again.
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.