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,556,491
Community Members
 
Community Events
184
Community Groups

project = HSV AND updated >= resolved

Edited
mike_bruderer_tg_ch
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!
Apr 15, 2023

Why that Operation doesn't work?

project = HSV AND updated >= resolved

I want to get a List where the Timestamp of updated is newer than the Timestamp of resolved. The case is, that sometimes a resolved Task get's an update, based on Jira is receiving a Mail with the Ticketnumber in the subject. 

 

I get de Message: 
Datumswert 'resolved' für Feld 'updated' ist ungültig. Gültige Formate umfassen: 'jjjj/MM/tt HH:mm', 'jjjj-MM-tt HH:mm', 'jjjj/MM/tt', 'jjjj-MM-tt' oder ein Zeitraumformat wie '-5t', '4w 2t'.

1 answer

1 accepted

3 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 15, 2023

Hi @mike_bruderer_tg_ch -- Welcome to the Atlassian Community!

Jira's JQL is not a SQL, and unfortunately cannot compare different issue fields in a query.

Some possible work-arounds may be guided by how frequently you need to perform such queries and willingness to purchase addons from the marketplace:

  • need this infrequently
    • export the issues to a spreadsheet and perform the query in the other tool
  • need this often, and do not want to purchase addons
    • investigate any free marketplace options which might help with such queries, or
    • pull/push the issues into another tool for queries, or
    • use an automation rule to detect/mark when this situation occurs (i.e., update after resolved) and then use JQL to report on that
  • need this often, and willing to purchase addons
    • investigate the marketplace for JQL and/or reporting addons to support this type of query

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer