Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Show Custom Fields in all Request types

We have two custom fields in our Jira Service Project and they show just fine in three of my request types but one of them, the Emailed Request, my custom fields are not available to put on the Issue view.  How can I add them as options to display?

1 answer

0 votes

@Nicole Wolf -

Here are the steps that you need to conduct -

1) Check your custom field configuration via Settings >> Issues >> Custom Fields UI  to determine if the field context are setup properly (i.e. is the field in question is exposed to all issue types (Global) in the system, or if it is exposed to all issue types used in your specific JSM project context)  NOTE - This can be done if you are the Site admin.


https://<your site>

2) Identify what issue types are used against your your JSM project's request types.  

3) If there are different issue types used, then you need to check your JSM's project fields configuration scheme to determine if those issue types have their own set of field configuration.

4) If there are different set of the field configuration schemes used by your issue types individually, then you need to check the issue's screen configuration scheme to ensure the field(s) are exposed in the screens (Create Issue/Edit Issue/View Issue).

NOTE - If your JSM project is "Team Managed" project type, then the custom fields that you created in the project are only local to the project itself and cannot be shared with other projects.

Lastly, In general - custom fields must be exposed to all applicable issue types and issue screens for the project first before you can add them to your request types screen.

Hopefully, you will be able to find your issues using the above suggestions. 

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events