Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Filter by parent, key, and due date

Renata Maciel
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 25, 2023

I am in need of a filter that can sort activities contained in multiple epics by due date, taking into account if they belong to the same epic. However, I am having difficulty because the filter currently sorts everything by due date only, without considering if the activities are from the same epic or not:

e.g. parent in (GQK-XXX, GQK-YYY, GQK-ZZZ) OR key in (GQK-XXX, GQK-YYY, GQK-ZZZ) ORDER BY duedate, parent ASC

2 answers

0 votes
Hannes Obweger - JXL for Jira
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Sep 26, 2023

Hi @Renata Maciel

welcome to the community!

Assuming that you are able to query the correct set of issues, I think you need to turn around the ORDER BY clause, to

ORDER BY parent, duedate ASC

... so it will *first* order by parent, and only within the same parent, order by due date - which I believe is what you want?

(Also note that Atlassian is making a few changes to how issue hierarchies work in Jira, so it may be that you have to ORDER BY "Epic Link" instead of parent... just in case that the above change doesn't work.)

Best,

Hannes

Have you tried issuekey in portfolioChildIssuesOf (ABC-123) where ABC-123 is the epic key?


or edit your query by adding quotes

(parent in (GQK-XXX, GQK-YYY, GQK-ZZZ) OR key in (GQK-XXX, GQK-YYY, GQK-ZZZ)) ORDER BY duedate, parent ASC

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events