Error trying to update story point with automation

[Hrag]

Hi,

My automation to update works perfectly for every field but story points.  For some reason Jira thinks I have multiple story point fields:

Found multiple fields with the same name and type: .

Story Points (com.atlassian.jira.plugin.system.customfieldtypes:float)

When I configure the automation rule and search for story point only one field shows up.

[Bill Sheboy]

Hi @Hrag -- Welcome to the Atlassian Community!

What type of project are you using: company-managed or team-managed?

Company-managed projects use the "Story points" field and team-managed use the "Story point estimate" field.  Have you confirmed you are using the correct one for your project type?

After checking that, if you are still finding multiple "Story Points" fields then possibly an admin has added additional fields which need to be investigated.

Kind regards,
Bill

[Hrag]

Hi @Bill Sheboy  Thank you for responding:

We are using: company-managed.  

Here's a screen shot of the automation rule (with some items redacted).  When this rule fires - a new story is created, it is assigned to the right person, its status is moved to in progress but the story point update fails with the error (more than one story point field).  How/Where can I see if there are multiple story point fields created through the admin?

[Bill Sheboy]

Hi @Hrag 

Would you please post an image of the audit log details showing any error which occurred?

Just to confirm, the project where this rule exists is company managed AND you are also creating the new issue in the same project, correct?

To check on the custom field duplication, as your site admin to navigate to the Jira System Settings, and then they can search for the custom fields configuration to see if there is a duplicate.  Here is the documentation to help with that assessment: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-custom-fields/

[Hrag]

Hi Bill,

I've been doing some more digging and the problem is that there are two story fields in my company managed project.    Both are under the custom field settings.  If I delete one of them then it seems to remove the story point field from my screens and gives me an error  (could not find suitable statistics field with ID customfield_10035).  So I restored that one back because it looks like it's the one that should be there.  When I remove the second one.  Then anytime I create a new story it auto creates this custom field again and just gives it a new ID number.  So if you look in my trash you will see all these "story point fields" that are automatically created by Jira anytime I delete a custom user story field :(.   The way the project stands as of right now is that it has two story point fields (one of them having id 10035 and the other 10052.  If I delete the 10052 then I only see one story point field on the custom screen.  BUT if I go and add a new issue then Jira will create a new story point field automatically and probably assign it ID 10053.  You can see in my trashed custom fields all the story point fields (none of these I've created).

[Bill Sheboy]

That appears to indicate that a site admin added another Story Points field at some point, and that caused the rule confusion.  Or perhaps some Jira migration process caused it.

Regardless of the initial cause, at this point I recommend submitting a ticket to the support team for assistance.  Otherwise repeated changes to that field might impact your built-in reporting and other story-point related functions.  https://support.atlassian.com/contact/#/