JQL for custom date field changes?

Question

Hello,

We currently have a custom date field (Target Ready Date) that we would like to be able to monitor for changes and run reports on. For example, and I'm not even sure if this is possible, we would like to know when this custom date field was changed, by whom, and what it was changed from. I know this can be done on a ticket by ticket basis, but I'm wondering if there are other means of doing this.

Is there a filter that can be created, or another method (report?), for easily being able to generate a report of some kind that shows these changes? Again, this is a custom date field and not a standard JIRA field.

Thank you!

Michael

Updated:

I'm sort of answering my own questions here (or providing a workaround). It looks like from research, you can't do any type of history queries on custom fields. So I'm guessing the answer to my own question is "no".

But as a work around, what if there was a new status created ("Date Change") that simply would loop from "In Progress" to "Date Change" and back to "In Progress".

Could you conceivably then run a "changed" report that queries the status field for that type of status change? E.g., get me all of the tickets that had the specific modification of "from In Progress to Date Change"? You could then potentially get the details on the date change from the ticket details, I guess.

How are others doing a similar type of thing?

Thanks,

M

unknown · Answer

Thanks @Ivan Tovbin for the reply. Unfortunately I don't control (or have much leverage) with our JIRA environment so I'm trying to work with what I have. I edited my initial question (which I sort of answered myself) but proposed a potential workaround using Workflow/Statuses. Do you know if that kind of a report based on the new workflow would work or not?

And out of curiosity, what 3rd party add-ons would you suggest for the scripting you propose?

Thanks!

Ivan Tovbin · Answer

Hi Michael,

I think this is totally doable with scripting, which however requires using 3rd party addons.

The general idea is that you could create a custom text field for example or a scripted field and then use scripting to extract you custom date field data (old value, new value, date of change, who changed it, etc) from issue history and put this data into your new field. Then you could display this field in your reports just like any other field.