Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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




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.

Screenshot 2022-12-30 at 1.45.32 PM.png


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


Select STORY POINTS field

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


Screenshot 2022-12-30 at 2.08.12 PM.png


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.

Screenshot 2022-12-30 at 2.08.45 PM.png


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!

1 comment

Thank You Thank You Thank You! 

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

Like Riley Sullivan likes this

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


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events