JQL Query showing Story Points when it shouldn't?

[Thomas Schlapp]

I've been trying to find a slew of stories in our project (RW) that have an empty story point field. 

I use this: 

(project = RW) AND (labels = aou-techdebt) AND (labels = upcoming) AND ("Story Points" IS EMPTY) ORDER BY "Story Points"

A lot of what shows, in fact, have an empty story point field. 

Some, clearly, have numbers listed (else I wouldn't be here asking). It is kinda weird. Any ideas? 

[Bill Sheboy]

Hi @Thomas Schlapp 

If you have ever used a team-managed (next-gen) project in your instance, you could be running into this custom-field confusion issue for EMPTY tests, as the story points fields are custom ones (although built-in): https://jira.atlassian.com/browse/JRACLOUD-76482

The suggested work-around is to use the custom field ID in your query to get the correct results.

Best regards,

Bill

[Trudy Claspill]

Could you possibly have more than one field called "Story Points"? You should be able to tell by starting to type "Story Points" in the advanced search JQL field. It will list all potentially matching fields.

Is this for a Company Managed project or a Team Managed project?

[Thomas Schlapp]

It isn't next-gen, just cloud.

We DO have more than one story points field. Interesting. We have: 

Story Point Estimate

Story Points 

Story Points

I guess I need to hunt down which ID it should be using for our project? 

[Trudy Claspill]

As a temporary solution you can simply change the name of one of those Story Points fields in Settings > Issues > Custom Fields. That should affect the display of the field in your projects and you should then be able to tell which field is actually being used.

You might also check the Screens that you see when your Create vs. when you are Viewing/Editing the issues. It is possible that both fields have gotten used; one on each screen. That could also be causing confusion.

[Thomas Schlapp]

Oh brilliant. 

Thanks for the guidance.