nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can a Filter capture Epics from which one or more Stories were created?

Phil Bustin_7fmhjs

For a Dashboard Filter Results gadget, I would like a Filter to define Epics from which one or more Stories were created.

For another Dashboard I would like another Filter to define JSM issues from which one or more Stories were cloned.

Can one or both such Filters be created?

Accepted answers

Trudy P Claspill

Regarding your first requirement:

Epics from which one or more Stories were created

Can you provide more detail on what that means to you? You can create child issues in an Epic and those child issues could be of the Story issue type. Is that what you mean?

For your second requirement you can use the Issue Link Type field to filter for issues that have a "is cloned by" linked issue. You won't be able to limit that to issue where the clone is only a Story issue type.

All comments

Trudy P Claspill

Regarding your first requirement:

Epics from which one or more Stories were created

Can you provide more detail on what that means to you? You can create child issues in an Epic and those child issues could be of the Story issue type. Is that what you mean?

Phil Bustin_7fmhjs

Can you provide more detail on what that means to you? You can create child issues in an Epic and those child issues could be of the Story issue type. Is that what you mean?

Yes, exactly. The only child will be a particular issue type that is a Story, as I understand it at the moment. (Does that anwer your question?)

There is one transition that triggers an automation that clones the JSM issue to a Story, so from what you say, I think the Issue Link Type will work in a Filter query. (Is that what you meant?)

Trudy P Claspill

For your first requirement:

There is not a native JQL function to retrieve a list of Epics where you get only Epics that do have child issues. That would require use of a third party app. Alternately you could add a custom field that keeps track (via an Automation Rule) of whether or not a child issue has been added to an Epic, and create a filter to select the Epics based on that custom field.

For your second requirement:

You could use a filter like this:

project=<your JSM project> and issuelinktype = "is cloned by"

Phil Bustin_7fmhjs

I should have been clearer: I'm trying to separate sets of issues (Epics and their Stories, JSM issues and their clones) by their very nature as unique sets, or by a field I populated in each set, "Global ID". That field contains the key of the parent item in each set.

I'm allowed a Query for defining swimlanes in a board, and I tried to define a query that would separate rows by a field ("Global ID") unique to sets of 1) Epics and Stories that were created from them as child issues and/or 2) JSM projects and the only Stories that were cloned from them. The query did not to create any swimlanes. One query that I tried and saved is

Project in ("Team BADD", "Level 1 Support (sandbox)") AND cf[10331] is not empty

where cf[10331] identifies the Global ID field.

I'm not surprised that no swimlanes were displayed, because I don't see how that query separates different values for Global ID, but I wanted to find out if there could be such a query.

I'm also interested in capturing the sets of related issues in a Dashboard, or separate Dashboards for JSM issues and their clones, and Epics and their stories.

Hannes Obweger - JXL for Jira

Hi @Phil Bustin

this is not about the dashboard gadget, but just to put this out there as a potential way forward: If you're open to solutions from the Atlassian Marketplace, both views should be easy to do using the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. These issue hierarchies can be modelled based on Jira's built-in parent/child-relationships (like Epic/Story), and/or based on issue links of configurable issue link types (like "is cloned by"). You can also configurable various filtering options, e.g. to hide any "empty" parents. With these, you should be able to build your views in no time.

This is how this could look in action:

We're first viewing epics with one or more child issues, and then switch to issues with one or more issues that are "cloned by". Of course you can also split these two views up into separate "sheets" - just as you prefer.

Any questions just let me know,

Best,

Hannes

Phil Bustin_7fmhjs

Thanks. I'll save this for when it's time to request Marketplace solutions. I appreciate the animated illustration.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

filter

dashboard