Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Seeing multiple Story points field

Pierre Laurac January 3, 2023

Hi everyone, 

 

We found that two fields are called roughly the same thing: `Story points` and `Story Points` in the Jira settings. 

This causes an issue elsewhere on our system and would love to get this fixed. 

This is *not* about `Story point estimate` which is also another field we have but do not causes any issues. 

 

Upon going to Jira / Settings / Issues / Fields, I do see the following Story points fields: 

image.png

 

That being said, I cannot find the `Story points` field any where in the custom fields list. Only `Story Points`:

image.png

Could you please let me know if I'm missing something obvious?

2 answers

2 accepted

0 votes
Answer accepted
Pierre Laurac January 4, 2023

Hi Nick, 

 

Thanks for the suggestion!

It was indeed a team-managed project but really hard to find. 

 

For future reference, what I ended up doing was to use the API:
- List all custom fields (It did list the two custom fields)

- the culprit custom field had a scope indicating the project ID.

- Listed all projects and found the project itself.

- Trying to delete via the API but receive a 404 error when using the ID returned by the API. I'm still unable to find the field in the UI to delete it.

Would you know why a 404 is returned here?

Pierre Laurac January 4, 2023

The actual error:

{

"errorMessages": [

"Field not found."

],

"errors": {}

}
Pierre Laurac January 4, 2023

We found a way to delete it from the UI (Next Gen project are quite different)

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 3, 2023

Welcome to the Atlassian Community!

The "system" story points field is not locked like the "story point estimate" because it does not need protecting against mis-configuration, bu it is the easiest (and hence best) one to stick with.

You are not missing anything obvious, it's just that someone has added "Story points" somewhere, when they should have just re-used "Story Points" to be consistent.

I suspect it has been added to a team-managed project, so it's going to be a bit of a pain to find, but try running a search for "Story points is not empty" (with the capitalisation you've got in your field list), this should at least tell you which project has it.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events