Versions Compared

Old Version 1

changes.mady.by.user Jeff Turner

Saved on

compared with

New Version Current

changes.mady.by.user Jeff Turner

Saved on

Key

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

Blogdisclaimer

Info

As of Tempo 10.19.0 this problem is fixed.See edit inline.


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

...

And likewise the view in the Excel-like Issue Editor plugin:

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 ) 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.

While that fixes the CSV export, for me it doesn't fix 'Issue Editor' values, which are still numbers. Perhaps I am just experiencing caching or some sort, or perhaps the Issue Editor plugin is doing something else weird. I'll update as I discover more.


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

Include Code
languagegroovy
urlhttps://gist.github.com/jefft/17a5270d51c685ee4d0c678dc9cc3b4e/raw/2023299c5bce2e631305fd356fd9aace1f511a15/tempo_team_name.groovy

Here it is:

This field can now be used in CSV and Issue Editor views to see the team names.