Is there a way to move Story Point Estimate field values to the Story Point field?

[Scott Buratt]

Need to move our Story Point Estimate field values to the Story Point field.

Is there a bulk way of doing this or is this just a manual walk-through?

Thanks

[Hannes Obweger - JXL for Jira · Accepted solution]

Hi @Scott Buratt

I believe you could solve this very elegantly with JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing and inline-editing all your issue fields. You can also edit your issue fields in bulk, using copy/paste. This works across any pair of fields, so you can very easily copy from one field to the other.

This is how this looks in action for "target start" and "start date"; it would work exactly the same for "story point" and "story point estimate":

You can update any number of issues in one action, so you should be done with your migration project in no time. (It's also worth noting that JXL can do much more than that: From quick sorting and filtering, inline issue creation, support for issue hierarchies, grouping, and sum-up. Disclaimer: I work on JXL :) 

Hope this helps,

Best,

Hannes

[Scott Buratt]

That's very nice.

Thanks for the info

[Trudy Claspill · Accepted solution]

The Story Point Estimate field is used only in Team Managed projects, and Story Points in Company Managed projects.

What is your scenario that you have both fields in your issues and need to move the data?

You could possibly do this through an Automation rule.

Create a rule with a scheduled trigger.

Define a JQL to select the issues that need to be updated.

Add an action to copy the data from the one field to the other field.

Add another action to clear the first field, if that is desirable.

[Bill Sheboy]

Hi @Scott Buratt 

Yes, and...to Trudy's suggestion:

I am hypothesizing you asked about this rule due to a migration from a Team-managed to a Company-managed project. 

In that case, rules can only process up to 100 issues at a time; that is the limit for automation rule processing (for branches, triggers, and lookup issues).  After the rule runs repeatedly on the schedule it would be "caught up" on this change by finishing all the issues...so perhaps add a condition and action to email you when there are no more issues to process, and then you can disable the rule.

Kind regards,
Bill

[Scott Buratt]

Thanks @Trudy Claspill , @Bill Sheboy ,

Correct, moving from Teams -> Company managed projects.

I'll look into automation (as I've not used that in Jira yet).

Appreciate the responses and thanks again.

...Scott