Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why are Plans so restrictive on what fields can be added?

Paul Madison
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.
June 12, 2024

Based on Atlassian's documentation -

https://support.atlassian.com/jira-software-cloud/docs/enable-custom-fields-used-in-advanced-roadmaps-in-jira/

 

We keep running issues with fields not being compatible with Plans and have to do silly/crazy things to work around the limitation.

Our most recent issue was with a Text Field (read only) that couldn't be added to Plans.

1 answer

1 vote
Sagar Mahajan
Community Champion
June 16, 2024

Hi @Paul Madison There is no official answer to this question but as Plan was not an inbuilt and was a external plugin previously so there are some limitations on the custom field types that plan was and currently supporting and this is also similar to the field types coming from the external plugins as those are also not supported with Plan.

There are some other factors that may have an impact on the plans to not support all the custom fields types.

  • Performance and Scalability
  • Consistency and Integrity with other Jira objects
  • Functionality Alignment

This is may be updated in future when Atlassian enhanced the functionality of plan

Currently below are the supported custom fields available to use in Plans

https://support.atlassian.com/jira-software-cloud/docs/enable-custom-fields-used-in-advanced-roadmaps-in-jira/

Suggest an answer

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

Atlassian Community Events