Since this issue is already marked as  `Not Being Considered` and is linked to https://jira.atlassian.com/browse/JRASERVER-27641   which is open, would be good to move these comments there.

I'm also looking for this feature 

Looking forward to this... 

+1 looking fo this

Agree that this would be helpful. it is difficult to drive some historical based metrics without this.

+1 very useful . Request for consideration in upcoming release. 

Would be a very good functionality to have in Jira.

+1 business impact
-1 performance side

+1, this is of great business impact . Please consider

This was opened 5 years ago.
277 savvy users were able to find this issue and vote for it.   That probably means at least double that number are interested in it.  Please review and provide some expectation for this feature request.  Thank you.

We are also interested to know further discussions about this, could it be considered now?

Gosia.Kowalska, it's been about a year, can this please be considered again?

+1.  We have a field similar to fixversion we use for planning purposes. We would like to see what is added to this field "Target Release Version" after a certain date. 

One may be able to add their custom field to the history index using component IndexedChangeHistoryFieldManager but when searching the allowed fields are hardcoded into the configuration.
ChangeHistoryFieldConfigurationManager.java > loadConfiguration()

Not being considered...looking at what is considered, we should not expect anything to come out then...

Disappointed with some frequent statements by the Atlassian team. That was opened in 2013 and will be reconsidered after 12 months? Removing vote. I'll do it by my self.

Hi everyone,

Thanks for your interest in this issue.

While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We appreciate the benefits of such requests, but don't plan to work on this for the foreseeable future.

This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.

Best,

Jira Server Product Management

+1

I installed a SIL Script Custom Field with the following script to get the last update made to a date field:

JFieldChange[] changes = getFieldChanges(key, "customfield_10000");

JFieldChange latestChange = changes[0];
date newest = latestChange.changeDate;

for (JFieldChange change in changes) {
if (change.changeDate > newest) {
latestChange = change;
}
}
return latestChange;

Need the historical searches which is imported for our business...

History searches for Custom fields is a very important enhancement that my organization requires. Please add this enhancement asap.

+1...

We want to track how many times 'dueDate' got changed for a task . Kindly help.

+1

We really need this feature on one of our custom fields to try and understand better the way our issues are moving about across different teams!  It would also be useful to have the 'Changed' historic search range too

I believe that this would be a great feature to have but I also believe Atlassian will never implement this.

Having such a feature would increase the index size substantially and will cause serious performance impact on medium and large scale systems.

Today we dont have an option to query JIRA history. This would be an great improvement for JIRA, if Atlassian include JQL to query customfields history on such as single select and multi select fields.

+1

So important. For us, we have user picker fields to track involved individuals on a ticket (that are not the assignee), and we really want the ability to send notifications like assignee if one of these custom name fields is updated. To do that, we need to be able to query on CHANGED TO with a time condition. Can't wait for this feature, hopefully it makes the cut.

+1
This feature would be brilliant for our teams. Can't wait to have this on-board.

+1

Same here: would be great to see this in JIRA core.

+1

Would be an extremely useful feature for us to utilize as well.

+1

Looking forward to this functionality.

Watching the issue.- would love a resolution to this.

Don't forget "level" field !!!

"Was" is a very powerful operator and not supporting custom fields is a shame. (All change history is kept in the same database table whether it is a system field or not so it should not be very hard to implement)

Hi Atlassian JIRA team,
Is this request on the roadmap this year? These types of filters/reports keep getting requested by upper management(Exec Committee, directors, vps) here at QAD and we keep telling them we can provide them this information. I would rate this a little higher than minor. The business value is certainly higher. Thanks for you consideration.

Regards,
Pat

As part of our release process after a specific date we lock down a specific release from any further code changes. We do have an exception approval process where a team member can request an exception from our configuration control board (CCB) to put a change in our release branch. We have a custom field which represents the states for the exception (CCB Requested, CCB Approved, and CCB Rejected). As part of improving our overall exception approval process, we would like to query when the custom field changes to the state such as CCB Approved. We have an ecosystem of over 300 developers who could be making exception requests and this would allow us to get metrics of when these requests are being made. With the current custom field that we have we can get the total count of exception requests that were approved but there is not a programmatic way to know when the request was approved.

We need it too! Currently there's no way to listen to all the changes on a custom field. When you have lot of people making changes on the same ticket, the only way to know who has updated it, is to go through the history logs manually. This process is tedious when you want to watch 100 tickets daily!

Cheers,
Nikhil

Yes, ability to do historical searches on custom fields of different types (select list, for example) would be a great improvement.

The best option would be if admins were allowed to specify if a custom field should be included into the history search or not. This ticket should include all history based operators, including:

CHANGED
This operator has the following optional predicates:

• AFTER "date"
• BEFORE "date"
• BY "username"
• DURING ("date1","date2")
• ON "date"
• FROM "oldvalue"
• TO "newvalue"

Thanks,
Joe