I want sum up how many issues that status was changed from "On Hold" to "At risk" between 2016-05-02 and 2016-05-06. I use syntax "Changed" and "During", but it filtered additional issues that status changed from "On Hold" to "At Risk" prior to 2016-05-02

[Frank Yu]

I want sum up how many issues that status was changed from "On Hold" to "At risk" between 2016-05-02 and 2016-05-06. I use syntax "Changed" and "During", but it filtered additional issues that status changed from "On Hold" to "At Risk" prior to 2016-05-02.

My syntax is project = ABC AND issuetype = "shopping" AND status changed from "On Hold" to "At Risk" AND updated >= 2016-05-02 AND updated <= 2016-05-06 ORDER BY updated DESC

[Chris Dunne [GetJirified.com]]

You can use the During operator

project = ABC AND issuetype = "shopping" AND status changed from "On Hold" to "At Risk" During ("2016-05-02","2016-05-06") ORDER BY updated DESC

[Doug Swartz]

Frank, here is an attempt to rephrase your request. Let us know if this is what you want:

List any issue which moved from On Hold to At Risk between 2016-05-02 and 2016-05-06 which is still At Risk at the end of the day on 2016-05-06 

If that is what you want, then this query should work:

Issue Changed from "On Hold" to "At Risk" during(2016-05-02, 2016-05-06) and status was "At Risk" on 2016-05-07

[Frank Yu]

Hi Doug,

Right now, I am tracking the historical record of "Open->Ready for Triage". As a result of your formula. there are two scenarios are inconsistent with the requirements:

1. This record was On Sat May 7, and should not in result list of 2016-05-02 ~ 2016-05-06.

        - 5 days ago

Status

Open [ 1 ]

Ready for Triage [ 10104 ]

        2. There were two records occurred on Fri May 6, but Open->Ready for Triage was first on Fri, then user changed its status Ready for Triage->Investigate. 

1 week ago

Status

Open [ 1 ]

Ready for Triage [ 10104 ]

 1 week ago

Investigation Details		Katie Ho to ensure this is required for initial go-live at Coastal sites.
Status	Ready for Triage [ 10104 ]	Investigate [ 10803 ]

[Frank Yu]

Thanks Chris,

I am sorry I might not make my question clear. The requirement is that the changed issue's final status can not be changed to other issue status (such as "Closed") due 2016-05-06.

For example, an issue status has the changing history:

Open->On Hold 2016-05-02

On->At Risk 2016-05-03

At Risk->Closed 2016-05-06

At the due day of statistics (2016-05-06) , the issue should be in the summary of "At Risk->Closed", the interim change status "On Hold->At Risk" will not go into the summary "On Hold->At Risk".

I know my requirement looks weird, but it is a real request from practical work, and more challenging for JIRA expert, isn't it?

Frank

[Chris Dunne [GetJirified.com]]

I am not sure I completely understand but it sounds like you want this

project = ABC AND issuetype = "shopping" AND status changed from "On Hold" to "At Risk" During ("2016-05-02","2016-05-06") and not (status changed from "At Risk" to "Closed" During ("2016-05-02", "2016-05-06") ORDER BY updated DESC

[Frank Yu]

Good idea to use "not" syntax. Well, if I have more than 7 status (Open, On Hold, On Track, At Risk, Behind Schedule, Escalated, Closed), and all issue statuses can be transitioned each other, I have to write 6 times of "not" in case of any exception status.

Could you pls translate the following idea into JQL syntax? Thanks.

If {

        issue type = "At Rsik" by 2016-05-06)

        If

            {

                 Issue Changed from "On Hold" to "At Risk" during(2016-05-02, 2016-05-06)

            }

    }