I suggest Structure should ...

Support 3+ Multi-Cascading Selects

Automation + Grouping on Multi-Cascading Select fields is a top-notch function that allows users to efficiently organize complex datasets, but are functionally limited to deeper organizations.

If I start using the Jira-system 2-tiered multi-cascading select field in Structure for my issues, but then decide I need to switch to a 3-tiered mutli-cascading select to model my data, I sacrifice the functionality of Structure for the flexibility of another add-on.

Including support in Structure for n+ Multi-Cascading Selects, e.g iDalko's multi-select field (using MySQL), would help users like myself fully harness the capabilities of automated issue structures

6 votes
Sign in
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Robin shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: facebook google
Signed in as (Sign out)
  • AdminStructure Team (Admin, ALM Works) commented  ·   ·  Flag as inappropriate

    Thank you for clarifications, Robin,

    We have such task in our backlog. We cannot provide an ETA as it depends on multiple factors but will let you know when the improvement is delivered.


  • Robin commented  ·   ·  Flag as inappropriate

    Hi Igor,

    The functionality you have described would greatly improve system multi-cascading select (n=2).

    I am also reaching for Structure compatibility with custom n+tiered cascading selects, such to the iDalko MC, which uses a simple database table to back-end.

  • AdminIgor Sereda (CEO / Founder, ALM Works) commented  ·   ·  Flag as inappropriate

    Hi Robin,

    Thanks for your suggestion. Do I understand you correctly, that the support for n-tiered fields that you are looking for is the ability of the grouper to replicate the hierarchy of the field's cascading values and place the issues in the the corresponding hierarchical buckets?

    If this is something else, could you please clarify?

    Thank you!

Feedback and Knowledge Base