Adding custom field support for version or version picker in JIRA plans
Asked by Kaustubh Deshpande:

Hi I'm trying to add a few more fields to our Team's JIRA Plan. I realize that there are a few unsupported fields, however, I'm curious why fields that have the \`Version Picker\` type are not supported when Release is support and that has a similar data type.   

Is there any planned support for these data type soon?


Answers:
author: Joseph Chung Yin
body: [@Kaustubh Deshpande](/t5/user/viewprofilepage/user-id/5444528) -

Welcome to the community. In Jira, the concept of version picker data type is based on Releases (also know as versions that project admins manages in his/her projects). Can you clarify more when you stated "version picker" type are not supported? I assume that you are trying to add custom fields to be included in your plan?

Another thing when using AR for Jira product, you also need to ensure that all the issues you are sourcing from for your plan, all have that specific field(s) exposed in the project or project(s). Example, if my plan pulls issue source from two different projects and the field in question is not exposed in one of those projects, then it will not be available.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: Kaustubh Deshpande
body: Hi [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739) thanks for getting back to me. So I'm trying to see if I can add these custom fields to the plan but they are under the unsupported category. I'm curious why these fields are unsupported but the actual release field (which seems like the same data source) is supported.   

Is the lack of support due to some other factor than type?  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/310658i52AF1AE66E132F09/image-size/large?v=v2&px=999 "image.png")


author: Joseph Chung Yin
body: [@Kaustubh Deshpande](/t5/user/viewprofilepage/user-id/5444528) -

Did you check

* Check the advanced roadmaps plan configuration settings to make sure the plan includes the projects and issue sources that use the your custom field. In the plan settings, go to the "issue sources" tab and verify that the correct projects and issue types are selected.

Here is the list of data types supported for custom fields in AR for Jira based on my knowledge -

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

Hope this helps.

Best, Joseph


author: Kaustubh Deshpande
body: Yes, this plan is sourced from on project and the screenshot shows that these fields are applied for all projects so that shouldn't be an issue right? Is there another way to find out why this is not supported? This indicates that the multi-version picker should be supported.


author: Joseph Chung Yin
body: [@Kaustubh Deshpande](/t5/user/viewprofilepage/user-id/5444528) -

You need to check the custom field's context to determine if it is applicable for all issue types used in your specific project or not.

Example, you are bringing in all issues types from a project, but this field is only defined for Task issue type and not other issue types used in your project.

Best, Joseph


author: Zev Ginzburg
body: [@Joseph Chung Yin](/t5/user/viewprofilepage/user-id/396739)

All of the checks you suggested are something I too have done and am experiencing the same exact issue.

I have all of the available fields with a global context with reference to version pickers, both single and multi.

Anything else I may be missing?

Thanks,


Tags: cloud

jira-software-cloud

plan

portfolio-for-jira-cloud

unsupported