Mapping the story points field between company-managed and team-managed projects?

[Gordon Bissell]

Is it possible to get a company-managed project (that uses the default "Story Points" field) to see the default "Story point estimate" field from team-managed projects?

We have a company-managed project (call it "MASTER") that we use to manage a number of other projects (both company-managed and team-managed); by setting the MASTER board's filter as such:

project in (MASTER, PROJECTA, PROJECTB, PROJECTC, ETC) AND issuetype in (Bug, Story, Task) ORDER BY Rank ASC

Tickets from all those projects appear in the backlog of the MASTER project, and we can drag tickets into sprints on that MASTER project. However, whilst tickets from company-managed projects (e.g. PROJECTB) show their story point value, tickets from team-managed projects (e.g. PROJECTA) just show a dash. Is there any way to get the MASTER project to use the "Story point estimate" field on those team-managed projects?

[Mikael Sandberg · Accepted solution]

The short answer is no, your main project cannot see the Story point estimate from a team-managed project. TMPs do support some global fields that are company managed, but Story points is not one of them. So currently your options would be to convert your TMP to a company-managed one in order to see story points on the main board. Or use a global number field and then in TMP use that field and either manually set it to the same as Story point estimate or use an automation to keep the two fields in sync.

[Gordon Bissell]

It's almost like Atlassian sat down and thought "how do we maximise incompatibility" when they invented next-gen/team-managed/whatever-it's-called-this-week projects.

It baffles me why they'd use a different field for the same thing in the two types of projects.