Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to implent user configurable three-level-cascading-lists?

We are trying to migrate a big development programm from another technologie to Jira.

One of the challenges is mapping their release-tree. 

They have about 100 release, each release with 5 to 20 Patches, each Patch with 5 to 100 Builds.

Packing all this into Release and using Jiras FixVersion(s) / AffectedVersion(s) doesn't look like a good solution. It would take ages to find and select the right element.

So we are looking for like a three-level-cascading list to select the right releas/patch/build.

But as there is a new build each week, we would need that cascading list to be adjustable/exendable by the user/administrators of that project.

Has anybody an idea how to implement such a thing? Or a completly different approach regarding our challenge?


0 answers

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you