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; } } }

How can I filter Stories with parent link ( epic) criteria being called in other query ?

erika assis

Hi, I have a query#1 to filter all Epics with specific characteristics and would like to build other query#2 to get all the stories related to this #1 query but I'm not quite there yet with nesting filters. Any hints?

Desired outcome : all the stories linked to the dinamic list of epics I get from "Filter1", as if in a simple declaration " Epic Link = "Epic Link" = "Filter1" and issuetype = story

Accepted answers

Kristján Geir Mathiesen

Hi @erika assis

So if your existing filter is called "Filter one" then you could do -> filter in("Filter one") AND here comes the rest of your criteria. Example:

filter in("Filter one") AND project in(example) AND issuetype = story

HTH,
KGM

All comments

Kristján Geir Mathiesen

Hi @erika assis

So if your existing filter is called "Filter one" then you could do -> filter in("Filter one") AND here comes the rest of your criteria. Example:

filter in("Filter one") AND project in(example) AND issuetype = story

HTH,
KGM

erika assis

Hi, thank you for your response!

Since "Filter one" only filters the epics, I can't use the issuetype = story. What I need to do would be use the "Filter One" as a "EpicLink" declaration, like : "Epic Link" = "Filter one" . But I don't know the sintax for it to be recognized

Kristján Geir Mathiesen

Sorry for a slow reply, @erika assis

I might be misunderstanding but you want @Filter One to include large enough data if you are going to be using a combined filter's search. On a Story, the Epic name is called Epic link. You should be able to do:

"Epic Link" = epic_name_goes_here

HTH,
KGM

erika assis

Hi Kristjan, yes! Let me write it better, currently in the filter recovering all the epic links - it's around 10 and might grow as new features are created related to the project. So instead of having to declare each epic link ID, I build this dinamic query that retrieves all the epics related to the project. What I want to do, is to use this query as a "epic link" call in the query where I want to retrieve all the stories related to all the current and future epics in the Epic query.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud