Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,636
Community Members
 
Community Events
185
Community Groups

How to Query Features (Epics) with all closed Jira issues, except for one specified project?

Using JQL how can I write a query that returns - for my project "LMNOP" - Features that have closed Jira associated issues, but exclude one specified project from the return?

I found this query which covers the first part of my question, but doesn't include an exclusion:

statusCategory != Done AND issueFunction in epicsOf("issueFunction in issuesInEpics("project = LMNOP")") AND NOT issueFunction in epicsOf("issueFunction in issuesInEpics("project = LMNOP") and statusCategory != Done")

I cannot figure out how to get the same return if I exclude one project from the return.

Essentially, I have a Feature that contains 2 projects and I only want to know when a Feature's issues are all completed with the one project, while the other can still have an issue(s) open?

Any help would be greatly appreciated!

I have tried to add a "AND project != QRSTV" in a few places around and within the query, but I'm really just missing the logical piece, so I don't even know if that is what needs to be added to make this query work how I want it to.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events