Converting Story Point Estimate to Story Points when migrating Team-Managed to Company-Managed

[Riley Sullivan]

Hello,

I'm hoping that this will be useful for anyone who are migrating from team-managed to company-managed Jira and needing to convert their historical story point estimate to the native Story Points field in their new company-managed Jira project(s). If this has previously been addressed or shared, I apologize in advance. It took me a while to figure this out on my own, and I was unable to find a solution searching online.

I am aware that the way our projects are organized perhaps isn't totally aligned with Agile etiquette :) 

Part 1

Getting the Story Point Estimate value moved to your new Company-Managed Jira project

Note: You do need to have admin privileges in Jira

After you have set up the basics of your new company-managed Jira project. When configuring your field screen, be sure to include the story point estimate field.

You are effectively mapping the "team-managed story point estimate" field to your "company-managed story point estimate" field when you add this field to the project. Thankfully this value does transfer to the new project, which it sounds like it historically hasn't from reading community threads.

Once you have moved your issues over to the new company-managed project you can move to the next step.

Step 2

Converting Story Point Estimate to Story Points

In the new company-managed project, you will need to build an automation. Even though the story point estimate value is numerical, the new project doesn't completely recognize it as such. So, in order to partly deceive your automation, you will need to create a smart value equation.

Below is the automation, I created it to be scheduled, and then manually 'Run rule' in the project to have a little more control.

SCHEDULE rule to execute

Then EDIT ISSUE FIELDS

Select STORY POINTS field

Set ({{issue.Story point estimate|0}}*1)

Then run the rule manually, or let it run on a schedule. The story point estimate field is copied to your Story Points field after it is finished. You may now delete the story point estimate from your project and use Story Points in its place.

I am aware that this is fairly specialized niche and might not apply to a bigger group. But I figured I'd write this to aid anyone in my situation!

[Tyler Kosaski]

Unfortunately, I think this applies to more situations than you think! My team will be using this information to copy story point estimates from a team-managed JWM to a company managed JWM. Thank you!

[Chathurange Jayasuriya]

Thanks @Riley Sullivan and @lorenzo_betto this worked as expected!

[Diana Silva]

I just needed permissions. I solved the problem 😉

[lorenzo_betto]

Found the solution for me! I was writing Set in the value but actually that was making the value non-numeric. This worked for me:

[lorenzo_betto]

For some reason I get this error:

[Riley Sullivan]

@Randi Rogers Glad this added value to someone else :)

[Randi Rogers]

Thank You Thank You Thank You! 

I was banging my head against the wall trying to figure this out. 

[Diana Silva]

Hello everybody 😁
Its my first contact with Jira and I tried this advices, but in my case I need solve another problem before it works. I have this messages for the field Story Points and the automation failed because that. We have 3 projects running with the same scheme. For 2 projects this field is not necessary. Any thoughts?