Tempo Ideas

Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.

Include display value of Elements Connect fields in CSV/XLS export

Background:

In addition to Tempo Timesheets, we use the following plugin in our Jira instance:
https://marketplace.atlassian.com/apps/23337/elements-connect-external-data-fields?hosting=server&tab=overview

By using this plugin, tickets in our system use an Elements Connect field to look up to an external database. Users use that field for the project code on their given ticket. Then, when they log work, they do so in Tempo to each ticket, and their work is associated with a particular project code.

Issue:

When we export tickets from Jira itself (Issues > Search for issues > Export), the Elements Connect fields display properly even in a CSV export.

However, when we export an Excel from Tempo Timesheets using the CSV or Excel exports, this value appears as the following:

{"keys":["4"]}

Rather than the display value, it is a key/database value.

Proposed Solution/Idea:

Include the display value of the Elements Connect field in the export, rather than the raw value.

  • Guest
  • Apr 20 2021
  • Future consideration
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files