I need to understand what % of our issues are getting deployed without moving through our QA process. Ideally, an issue status goes from In Progress to QA Ready to QA Started to QA Complete before being changed to Merged and then Deployed. Issues that bypass our QA Process will go straight from In Progress to Merged and then Deployed.
What would the syntax be for identifying recently resolved issues (say, in the last month) that moved through our QA statuses?
Hi Becky - Welcome to the Community!
You can do the query as you want for the list of issues that are resolved (for whatever time period you want) and then add "and status was in ("QA Complete") or whichever of the statuses you want to identify. Usually in the case you have identified, I use status was not in ("QA Complete") which shows the issues that did NOT go through QA Complete.
So it would look something like this, status changed to Resolved during (yyyy-mm-dd, yyyy-mm-dd) and status was not in ("QA Complete").
Where Resolved is the actual status name you use and the dates are the time frame you are looking for.
Hope that helps. If you have trouble with the syntax, holler back. :-)
Wow thank you @John Funk that's exactly what I needed. Turns out that these queries did the job:
status changed to "deployed" during (2019-01-01, 2019-03-25) and status was in ("QA Complete") and project = Product
comparing to
status changed to "deployed" during (2019-01-01, 2019-03-25) and status was not in ("QA Complete") and project = Product
To understand what % is making it thru the process.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wasn't able to pull resultant even if the syntax and other seems to correct.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Devi - Please create a separate question and provide the details of what you need. That way more people will see it. You can tag me on it if you like.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.