Story point and story point estimate (duplicate?) fields

[Alexander Brockhoff]

Hi all

On my Jira Cloud instance I have two fields, one called Story Points, one called Story points estimate.

The Story points estimate field is reserved in the custom field view so that I cannot delete it, while the Story Points field is not. I took this to assume one was custom created while the other was from Jira.

However, it seems Jira by default is using the Story Points field on the views for my issues and in the reporting for velocity etc. 

Is there something I am doing wrong? What is the proper use of each field? The estimate field doesn't make much sense to me as a field since the Story Points field seems to track changes to itself over time/in a sprint.

[JamieA]

Well, it will be the intersection of the result sets not the union because you used AND not OR, but I know what you mean.

>  is that an indexed lookup of some sort that would make it somewhat efficient since there is not project qualifier for the versionMatch function?

I wouldn't anticipate that to be slow in any way because it will resolve to Reported Release in (\[some list of versions]), where that list is calculated from the reg ex.