[#JRA-7936] Add 3+ level cascading custom field type

JIRA

Add 3+ level cascading custom field type

Created: 13/Sep/05 08:45 PM Updated: 17/Aug/08 07:28 PM

Component/s:

Custom Fields, Custom Fields (new types)

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-15427~~ Custom Fields incompleteness

~~JRA-7652~~ Remove limitation of two levels in cascade in cascading select field or extend field context (multi-level cascading select)

Participants:	Anton Mazkovoi [Atlassian], Benjamin Naftzger [Atlassian], Dan Corey, mark west and Paul Csapo
Since last comment:	43 weeks, 5 days ago
Labels:

Description

« Hide

A large 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?

Vote for this issue if you would like to see this implemented sooner rather than later.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dan Corey added a comment - 01/Nov/05 06:19 PM

I specifically mentioned three only as an example, but I'd actually prefer to see what you outlined, having this up to a whatever level I designate (within reason, of course).

[ Permlink | « Hide ]

mark west added a comment - 02/Oct/07 09:12 PM

Hey Dan,

I was after this as well, and came across this plugin. http://confluence.atlassian.com/display/JIRAEXT/Multi+level+cascade+select

Haven't tried it out yet, will let you know how I go, or if you get there first?

May be it will get taken on board but Atlassian?

Hope this helps

Mark

[ Permlink | « Hide ]

Paul Csapo added a comment - 10/Dec/07 01:13 PM

Dear Atlassian, it would be great to have this feature within JIRA itself, and as a supported feature.
Do you have any idea when this could be incorporated?

kind regards,
Paul

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 11/Dec/07 02:39 AM

Hi Paul,

I know that there is a plugin that fixes it, however, in the past we have found that the time needed to commit contributed code is quite similar to the actual implementation of the feature. The main reason for this is that we need to ensure that the code works in all cases, for example, when the field is configured differently for different project/issue type pairs, when an issue is moved or bulk moved between these projects, etc. We also need to ensure that the code is well tested so that it will continue to work as JIRA is extended.

Due to this reason and the number of feature requests and their popularity, at the moment, we do not have an implementation date for this.

Thanks,
Anton