Skip to content

I suggest Structure should ...

← Structure for JIRA: Ideas

Granular control over Automation grouping, particularly with Labels

Currently, grouping within Automation is kind of an "all or nothing" approach. For example, we use labels to identify which "product" our epics are for, but we also use the Labels field to track other information. For our main Structure, what we want to do is have the Automation grouping only look at the 6 labels we currently use for "product" tracking and ignore all of the others, but I cannot seem to find a way to do this without manually creating my own folders and setting up the Automation for each one; the drawback to this is we can't drag an item from one folder to another and have it automatically apply/remove the applicable labels, not to mention how much longer it takes to set up the folders individually versus a single set of Automations.

5 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Josh Neiman shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Mikal H Henriksen commented  ·   ·  Report

    S-JQL works for this when used as a (quick) transform! But it would be fantastic to be able to use it as automation too, so that I can scope it to a specific folder more easily (because that's also already possible just by extending the S-JQL in the quick transform to also match everything outside that folder). Right now when I add a S-JQL filter as automation it seems to only affect issues, and I can't move it below the grouping automation.

  • AdminJulia (Product Owner, ALM Works) commented  ·   ·  Report

    Hi Josh,
    Thank you for your reply!
    Good usecase, there is no simple way to resolve it. But we have our built-in language, S-JQL, which helps to work with groups, too, could you please take a look: https://wiki.almworks.com/display/structure/S-JQL+Reference? Do not hesitate to ask our support team to help, support@almworks.com.

    Julia,
    ALM Works team.

  • Josh Neiman commented  ·   ·  Report

    I did try that and it didn't achieve the desired result since that's just filtering the issues, not the groupings created.

    Here's an example of what's going on using generic info:

    Issue: Work on Feature
    Labels: Product A, Product B, Timeline, Team A, Team B

    Desired structure grouping
    Products {Automation with grouping by Labels}
    --Product A
    -----Work on Feature
    --Product B
    -----Work on Feature

    What happens when I try to set it up this way is it creates groups for all of the labels on any issue present within the Product folder; for the example issue, that would be groups for Product A, Product B, Timeline, Team A, and Team B. If I applied a Filter Generator focused on removing the label "Team A" it would remove any issues with that label, which would prevent it from showing up as a group but also defeat the purpose.

Structure for JIRA: Ideas: Structure

Categories

Feedback and Knowledge Base

(thinking…)