Compare all fields on a ticket between 2 dates

[Eric Levin]

I am trying to use JIRA for project reporting. Say I have an story ticket. That ticket has an evolution. I'm wondering if there is a way for me to compare that ticket to itself on 2 dates.

Example:
on 1/1/2019
Key: ABC-123
Title: Project Alphabet
Summary: something
Start Date: 1/1/2019
Due Date: 2/1/2019
...

on 4/1/2019
Key: ABC-123
Title: Project Alphabet
Summary: now this is different   <--changed
Start Date: 1/1/2019
Due Date: 5/15/2019  <-- changed
...

Is there an easy way for me to know that, when comparing ABC-123 on 1/1/2019 and 4/1/2019 the due date and the summary were changed? Is there something native to JIRA that will do this or even a plugin?

[Andy Heinzer]

Jira's native JQL searching can't compare two date fields with each other to return issue results.   However this kind of question has been asked before here in Community, check out https://community.atlassian.com/t5/Jira-questions/JQL-Compare-Dates-Created-vs-Updated/qaq-p/339675

In it, users have suggested some different addons to Jira that might help here.  There are likely more possible solutions to this, but I know that Scriptrunner has a dateCompare JQL function that you could to build a JQL query to compare date values to each other.  That might help to some degree here.

But there isn't really a good way to search the historical values of all fields in Jira.  Jira's JQL does have a WAS operator, however this is limited to only being able to work with a select few system fields in Jira.  It doesn't work with custom fields or any date fields to my knowledge.

You could use a plugin like scriptrunner just to find issues that have a specific length of time between them to start.  And from there, you could open each issue of concern and look at the history tab.  That tab contains a list of all the changes to the issue over time. So it might still be possible for you to find out when a field value was changed on a Jira issue and by which user, but these kinds of details are not always easily searchable in Jira's JQL itself.