Some custom field values don't show in Jira Cloud Advanced Roadmaps plans

Nina Barley
Contributor
March 17, 2023

I have several custom fields, all defined to screens and projects. Some of them are available to display in Jira Plans and a couple are not. I have tried everything I can think of to get these additional custom fields to show up on our roadmap.

When I try to add a custom field to Jira Plans (Roadmap), this is what I see. As you can see, the field called "prioritization score" is not on the list.

add-custom-field.PNG

This one shows up:

Doc Reporting.PNG

This one doesn't:

Prioritization score.PNG

3 answers

1 vote
Oday Rafeh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2023

Hi @Nina Barley 

In jira cloud advanced roadmaps, not all custom field types are supported for display in plans. If the custom field "prioritization score" is not showing up in your plan, it might be because the field type is not supported.

You can try:

Check the custom field type: go to jira administration > issues > custom fields and locate the "prioritization score" custom field.

Verify the field type and check whether it is one of the supported field types in advanced roadmaps.

Supported field types include:

  • text field
  • number field
  • date picker
  • date time picker
  • single choice select list
  • multi-choice select list
  • single version picker
  • multi version picker

If the custom field type is not supported, consider changing the field type to one of the supported types or create a new custom field with a supported type that can be used in your plan.

If the custom field type is supported, ensure the field is correctly configured and associated with the desired projects and issue types. Sometimes, configuration issues can cause custom fields not to appear in plans.

Make sure your plan is configured to include the projects and issue sources that use the custom field. Go to the plan configuration settings and verify that the custom field is available for the selected issue sources.

Nina Barley
Contributor
March 17, 2023

The prioritization score field is a number field, which according to the list you cited above, is supported. It is associated with the same projects and issue types as the doc reporting field (which I was able to add to the Plan).

Oday Rafeh
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2023

Hi again @Nina Barley 

Since the "prioritization score" custom field is a supported field type and associated with the same projects and issue types as a working field, there might be an issue with the configuration or a bug in Jira cloud advanced roadmaps. To troubleshoot further, try the following steps:

  • Check the field configuration scheme for both the "prioritization score" and the "doc reporting" fields. Make sure they share the same field configuration scheme and have the same settings.
  • Re-index your Jira instance, as sometimes, indexing issues can cause unexpected behaviour. To re-index, go to Jira administration > system > indexing and click on "re-index. "
  • Check the advanced roadmaps plan configuration settings to make sure the plan includes the projects and issue sources that use the "prioritization score" custom field. In the plan settings, go to the "issue sources" tab and verify that the correct projects and issue types are selected.

If the problem persists, consider reaching out to Atlassian support for further assistance. They might be able to identify a specific issue or bug that's causing the custom field not to appear in the plan. 

And I apologize for not being able to resolve the issue for you

0 votes
Bas Diender
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 6, 2024

Just in case anyone (like me) stumbles upon this thread with the same problem: The solution in our case turned out to be pretty simple (but hard to find).

 

In the Configuration of the field that did not show it's value we changed the search template from 'None' to 'Number Searcher' which made the values show up in Plans.

0 votes
Nina Barley
Contributor
March 17, 2023

After fiddling with this for most of the day, and trying all the solutions the wonderful people in the community suggested, I finally decided to just recreate the field (brand new), and copy over the values (a little tedious, but better now than later). This seems to have worked fine. The original field must have been corrupt.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events