• Community
  • Products
  • Jira
  • Questions
  • 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

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

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

 

3 answers

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

 

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

 

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

StatusOpen [ 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

 

StatusOpen [ 1 ]Ready for Triage [ 10104 ]
 1 week ago

 

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

 

 

 

 

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

 

 

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

 

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)

            }

    }

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

468 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you