Is using the Tempo Team field a bad idea?

[Ian H]

We are finding this field very limiting in that it is not available in Automation.

We have 6 teams working in our project and we want use the team field to signify ownership, and also for capacity / release planning.

We use Aha! for roadmap management and have built an interface with Cherwell for Support reporting bugs. But using the Tempo Team field feels very problematic for both of these integrations and most workarounds we try to implement using Automation won't work as we had hope. For example we can't find a way to use this field in an issue field comparison.

Have we made a mistake here. Should we have used a different field to signify which team "owns" a specific epic or bug?

Would really appreciate the benefit of experience for any other users.

[Ste Wright]

Hi @Ian H 

It might be possible to still use the Tempo Teams field as long as you can confirm the...

• Custom Field ID - usually possible even on locked fields by viewing the field information, and taking the ID from the URL
• Team IDs/Names

If you're using the Team field from Advanced Roadmaps - to set this in Automation using an Edit Issue action you...

...Select "More Options" then in the Additional Fields section enter:

{
"fields": {
"customfield_10123":"5"

    }
}

^ In this example, 10123 is the Team field's custom field ID, and 5 is the Team ID

I'm not sure exactly how this might translate to Tempo Team field, but this might get you a little closer :)

Ste

[Ian H]

Thanks Ste

I have indeed used this approach for setting the Tempo team field, but can find no way for example to use the field in a condition and can also find no way to set it via interfaces from other applications such as Aha!

I fear I am going to end up creating another Team field for this purpose and then set the Tempo field using Automations. But my concerns with that is the number of Automations I need to set and the concerns about breaking that if teams are changed/added (which sadly we do all too often).

[Ste Wright]

Hi @Ian H 

For using the Tempo Team field in those other scenarios, I'd probably recommend clarifying this with the vendor directly.

You can contact Tempo using the options listed on their Marketplace listing's support tab 

---

Whilst an additional Team field is not ideal, if you do end up doing it - I'd consider either...

• Using Team from Advanced Roadmaps, if you have Premium, or...
• Using a Select List custom field type. This would limit who can modify the options - and allow changes (and their corresponding Automation rule updates) to be tracked via the central Admin team

The benefit of Team from Advanced Roadmaps is each team receives an ID. This means it doesn't matter what the name is changed to, as long as it's clear which Team the ID references.

If Tempo Team also has an ID, you could create a relationship map between the two fields. This means only addition / removal of Teams would need to be managed for.

---

Let us know your thoughts!

Ste