I think this is a more of a bug than a suggestion.

In the backlog view, the bubble on hover says it's the Story Point value, but under Fields it is the Estimate toggle that turns it on and off. There is no way to say it should show Story point estimate.

I have the same use case (and problem) as @stefan-seervision. 

Is there any workaround for being able to have a backlog show story points from both company and team managed projects?

I'm so confused. We just bought premium for Advanced Roadmaps, and I have no idea which story points fields we should be using to make this work. Which field are we supposed to be using?

I had an automation to sync the two story point fields which was working fantastically! Until a week ago...

Now it gives this error:

Action details:Multiple issue events
Rule was triggered by event:com.codebarrel.automation.trigger.multiple.created
Edit issue
Could not find your configured field, it may have been deleted, or may need to be added to the project "Story Points"
No fields or field values to edit for issues (could be due to some field values not existing in a given project):ED-2184 

iteong, With Team Managed projects getting official support in Plans (Advanced Roadmaps), and the Plans supporting a harmonized Story Points column, can we expect this same level of support in the backlog and reports soon? 

Is this going to be worked on? There's no documentation covering the difference between these fields, and responses from Jira support in forums are conflicting and contradictory. If the recommendation is to use the Story Point Estimate field, why doesn't it show up in any of the issue lists of sprint reports?

you know, Atlassian, be agile... get a way to display SP across projects, really... Your "workaround" does not work anymore.

It's impossible to have a company managed project that contains tickets that are also in a team managed project and for reporting to work or for boards/backlogs in the company managed project to show story points (because they are story point estimate in team managed project). Really unhelpful. Considering migrating team managed projects to company managed projects to resolve it

Is this issue being worked on?  We ran into this problem in sprint 1 of our next gen project.    Is there a documented workaround?

Greetings!

If this is ever fixed...please lean way forward to notify customers, as this has the potential to break automation for Jira rules and REST API users.  Some automation rules could be automagically fixed by coalescing these fields, but other rules which handle both CMP and TMP projects could not; those will require customers to manually update and test rules.

Thanks, and kind regards,
Bill