We are currently upgrading Tempo to Tempo 7.9.2. One of the problems we're encountering is the renamed Team Custom field. In our Enterprise, we had separated groups that used Tempo by having them use the default "Tempo Team" custom field while groups that aren't using Tempo for time-tracking were managed by a standard JIRA custom field called simply "Team".
Testing the upgrade, we came across several warning messages from our database about not knowing which "Team" value to draw from. In our case, it's not just filters but scripts, listeners and external WebFocus reporting that pulls from those two fields.
Is there some way that I'm not seeing about renaming that Tempo field back to "Tempo Team" rather than the automatically created, and locked, "Team" name? For us, that would be a lot less work than changing everything referencing our JIRA "Team" field.
in the System Plugin: Tempo Teams 2.3. that comes bundled with Tempo Timesheets 7.9.2, you can rename the Teams Custom Field. This is done in the Tempo Administration, Tempo Teams, Team Field. Please take a look at https://tempoplugin.jira.com/wiki/display/TEAMS/Team+Field for more information.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs