JQL Updated items that have been re-ranked

[Mike Winston]

I would like to know how to filter in JQL for all items that have been changed in the last couple days, including items that have been re-ranked.

Background: I am creating a forecasting tool based on story points and rank in the backlog.  Our JQL is doing a standard 'updated > "<calculated date>"'.  This returns all items that have changed story points or manually changed rank.  But if there was a conflict in the rank value and JIRA automatically changed the rank value for the issues below the re-ranked item, this does not show up in my query.  So I end up with multiple items with the same rank, since i only update the items in my list that are returned from the query.

How do I get my query to return all changes, even backend changes to the issues?

[Andy Heinzer]

When a user changes the rank of an issue, this is logged in the issue's history tab.  However when the system has to change the rank value, due to a rebalance, or error correction, these events are not actually logged on the issue, nor is there an event fired by the system regarding that issue. 

End users are not expected to know the exact rank value for any issue.  Jira can do rebalancing on the system which has the potential to change the actual value of that field for all the issues, but this doesn't actually change the rank of the issues in relation to each other.   In addition to that, you can't search in JQL via the historical value that field had for issues.  

What this all amounts to, is that I can't see a way to do what you want with native Jira alone.   But I would like to know more about what you are trying to achieve here in case there is another avenue we might be overlooking.

Could you tell me some more details about the JQL filter you are using here?

I don't quite understand how it is you are having issues with the same rank here?  Typically when an issue is created in Jira, it is given an initial unique rank.  And in turn all the changes that Jira would make to a Rank field are expected to keep issues with unique values.  Having duplicate rank values for issues is a problem, so I'm concerned to see if perhaps you're using an unexpected plugin in Jira in order to either create issues or modify their specific rank values for some reason.