Dear all,

I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

Sincerely,
Aakrity Tibrewal
Jira DC

This one really surprises me- as a company that does time tracking through Tempo and planning with Advanced Roadmaps, it would seem an obvious opportunity to integrate this functionality together for better planning and tracking.  The same "teams" you define in the "Teams" tab could be selected and used for team permissions in a project, assigned teams in Advanced Roadmaps, and teams within Tempo for tracking.

You would think that by now, Atlassian and Tempo could have worked this out, but no, still a cluster"(#)#%. I'm so tired of explaining this mess to people.

Get together, buy each other some beers, and solve this.

While you're up, try to improve compatibility between AR and Tempo too

We purchased "Extender for JIRA" to resolve another issue we had.
https://marketplace.atlassian.com/apps/1217643/extender-for-jira?hosting=datacenter&tab=overview

Found it has a neat little feature that lets you unlock a custom field and rename it. So far we haven't seen any issues doing this.

We encountered the same situation using Jira Advanced Roadmaps & Tempo Teams.
Our solution was to rename the Tempo Team custom field from Team to Tempo Team. You can do this in Tempo Teams Configuration.
We then use Jira Automation to keep the two fields in sync. Unfortunately, you can't update the Team or Tempo Team fields directly, so we have to use some JSON in the Additional fields box in the automation rule.
It isn't the most elegant solution. But, I wanted to share our workaround in case others can use it.

This is a cluster"(#)#%. Information like team is crucial for many applications in team based organizations and frameworks. There simply is no justification to duplicate the field instead of allowing either of the tools to map the field from other or incorporate the team field as system field that these tools share.

If there ever was a way to implement this in worst possible manner, this was it. Imagine if one of the tools crashed the jira server instance when you tried to uninstall it to avoid this problem.

As Advance Roadmaps is part of Jira Software Data Center since Feb 2nd 2021, this problem is now also targeting our JIra Software Data Center instances as we are Tempo Timesheets customer since multiple years.

What is the idea at Atlassian to handle this now double available custom field? For administrator is is nearly impossible distinguish between both of them. And if really both are needed in projects it is also more then confusing to the end users.

I believe, as Tempo is older then Portfolio/Advanced Roadmaps Team custom fields. Atlassian would have the chance to find a solution on this together with Tempo as one of their biggest App Partners to find a solution that best fits to their customers.

But it seems so that you left your customers alone with this problem

Since a few weeks, Atlassian introduced a new Team (custom) field for their portfolio add-on that conflicts with our existing Team field from Tempo.

Having two custom fields with the same name has the effect that in filters you see cf[10740] and not Team which makes filters quite unreadable.

We did not ask for this "new" Team field to be added and are now confronted with a degradation in usability.