Hello everybody,
I want to show tickets with status "Resolved" in Service Desk Project and assignee baris.ozer between 01 January 2022 - 31 December 2022.
Is the JQL Query I made below correct?
project = SD AND status = Resolved AND assignee in (62069a8aed02400069a3ad5f) AND created >= "2022/01/01" AND created <= "2022/12/31" AND resolution != unresolved ORDER BY created ASC
Hi @Barış Özer
Can I confirm the logic for your rule is:
---
If this is correct, this should work:
project = SD AND status = Resolved AND resolution is not EMPTY AND assignee = 62069a8aed02400069a3ad5f AND createdDate >= startOfYear(-1) AND createdDate <= endOfYear(-1) ORDER BY created ASC
or with static dates:
project = SD AND status = Resolved AND resolution is not EMPTY AND assignee = 62069a8aed02400069a3ad5f AND createdDate >= 2022-01-01 AND createdDate <= 2022-12-31 ORDER BY created ASC
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Barış Özer
Yes, yours also works the same way :)
I usually avoid "Unresolved" in resolution queries, in case someone creates it as a resolution option!
But your JQL should produce the same results as what I suggested.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright
I only need statuses that are "resolved".
This is why resolution != unresolved exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright
This JQL Rule looks nicer and readable.
project = SD AND status = Resolved AND resolution is not EMPTY AND assignee = 62069a8aed02400069a3ad5f AND createdDate >= startOfYear(-1) AND createdDate <= endOfYear(-1) ORDER BY created ASC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Barış Özer
Just to clarify, Status and Resolution are two different fields.
If you're looking for just Issues with a Status of Resolved, and the Resolution can be set to anything (including empty) - then the "resolution is not EMPTY" part of the query is not required.
To see how Status and Resolutions differ, see this help page: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-statuses-priorities-and-resolutions/
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.