-
Suggestion
-
Resolution: Unresolved
-
1,179
-
127
-
Hi everyone,
Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.
Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.
As a workaround, there are excellent marketplace apps available that provide customizable fields, including the ability to create cascading fields. Please have a look at the following apps:
- Multi Level & Tree Fields by Almbase for multilevel custom fields
- Awesome Custom Fields but Seibert for custom fields
We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.
Ahmud
Product Manager-Issue View
aauleear@atlassian.com
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. There are a number of add-ons on the Atlassian Marketplace available to support this. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
A customer requested cascading fields that have more than 2 levels of variables. They specifically requested the ability to have up to a 3 level - 4 level deep cascading field list.
Perhaps this could be programmed in such a way that would easily allow customers to add as many levels as they wished?
Workarounds
Forms
Using Jira Forms
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
[JRACLOUD-7936] Add 3+ level cascading custom field type
This is just the tip of the iceberg...
Atlassian needs to revamp their entire set of fields that were only prevalent in the 90's.
I have listed a few here just so you understand how outdated Jira is when it comes to fields and forms:
One more to the list of simple stuff that all systems have, but Jira...
Yay!
Hello,
This update would literally be a revolution and a time-saver for my team. I've tried to test solutions available from the Market, but the reports don't take these special fields into account or the display is rotten. Even the use is completely uncomfortable...
Do you have an idea of when this system should be implemented? You can't refuse us after all these years ! 
our console contains 100+ service names(options), and will keep on increasing more and more, which current situation is the 100+services names list in the Child layer. This makes user very difficult to select correct option when transfer case between different teams, because the system user are more than 2000 seats, which also lead to wrongly escalating to target team, and delays the case handling
Jesse Stephenson, did you mean 19 years instead of 9, right? 
This ticket is older than my kids!
And again, I don't know why Atlassian won't improve the entire set of Jira fields. We not only need improvements to the existing ones to support more cascading levels among other things, but we also need new ones to match the current internet form standards out there - not the fields from the 90's currently offered by Jira.
Yup definitely want this. How has is it not added after 9 years? Just leaving it to the Atlassian Marketplace?
This feature should be a out of box feature of Jira Service Management.
2 Level cascading not enough for lots of cases .
Please do not tell me to use a third-party app when my company is spending hundreds of thousands of dollars on a solution that should have native fields supporting basic customers needs.
The current set of fields Jira offers looks like a CRM tool from the 90's. I actually used a tool back in the day called "Vantive" which had the exact same fields Jira offers.
Atlassian needs an awakening when it comes to Jira fields. What we have now is almost pre-historic.
This was requested in 2005? You 'all know its 2025 now, right? Feels like this could have been added in the last 20 years.
You increase the cost of Jira every year, and you recommend a paid app?
As a workaround, there are excellent marketplace apps available that provide customizable fields,