JIRA query to find when the issues status is getting changed from statusA to StatusB but not statusC

[Kannan Sundaram]

I used this query: 

project = "XXX" AND issuetype in (Bug, Spike, Story) AND Sprint in openSprints() AND status changed from "IN Coding" to "IN QA" during (2019-02-22, 2019-03-07)

It is fetching the results correctly. Means it is giving the right date when a story is getting ready for QA in Issue calendar widget.

But if the same issue's status gets changed from "IN QA" to "PO Approval" then this query is picking the latest status update date and showing this issue on different date in the issue calendar widget.

Say: If a story status is changed from IN Coding to IN QA today(26-02-2019) then in the issue calendar widget it shows the story against today date. but after 2 days, if the same issue status is changed from IN QA to PO APPROVAL then the same issue is moved from today's date cell to 28-02-2019 date cell (today + 2 days) in the issue calendar widget.

How to have the query which is not considering the status update happening after "IN QA".

Or 

How to ignore the any status updates after IN QA.

workflow: Open>>Analysis >> IN CODING>>IN QA>>PO APPROVAL >> Done

Please help!!!

Thanks,

Kannan

[Andy Heinzer]

Jira's JQL searching is designed to return Jira issues.  And technically it's doing that here.  But I understand that you're wanting specific issues be returned and not be effected by the possibility that the same issue could be transitioned multiple times between these transitions.

I'm not sure that JQL itself can solve this problem by itself given the way it is designed.  But I'm interested more to investigate the way you are using the Jira Issue Calendar gadget.   If you go into your dashboard and edit this gadget, you will see that in addition to specifying a filter to select Jira issue, you can also select the field 'Date to Display'.  This can be any date or date/time field in jira.  Are you currently using the 'Updated' option here?  If so, then perhaps it would be better to use something like Due Date, or create a new custom date field for these issues and set on them a value that might be dependent on the first time this transition is executed.  Maybe that could help you avoid these issues appearing on the calendar with a different date than expected.

[Kannan Sundaram]

Hi Andrew,

Thanks for the suggestion. Yeah, I'm using the 'Updated' option here. Will try to play around with due dates field and share you the results soon.

Cheers,

Kannan