Versions Compared

Old Version 5

changes.mady.by.user Jeff Turner

Saved on

compared with

New Version 6

changes.mady.by.user Jeff Turner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

As of Tempo 10.19.0 this problem is fixed. In earlier versions issue.getCustomFieldValue()  on a Team field returned a text string of the team id ("53"). In 10.19.0+ you now get a com.tempoplugin.team.api.TeamImpl  object back, whose toString()  returns the team name. Thanks to the Tempo devs for (eventually) doing the right thingSee edit inline.


Tempo has a Team custom field. Here it is rendered in the Issue Navigator:

...

I have reported this as a bug to Tempo (10.17.x) but it's basically "Won't Fix". The field's native representation (i.e. issue.getCustomFieldObjectgetCustomFieldValue() ) is a String like "52".

Info

Edit: This is now fixed. In Tempo 10.18 and earlier, issue.getCustomFieldValue() returned a String like "52". In Tempo 10.19+ you now get a com.tempoplugin.team.api.TeamImpl  object back, whose toString()  returns the team name.


Fortunately we have ScriptRunner. Here is source for a Script Field called Tempo Team Name which renders the actual team name:

...