Is it possible to associate unique Employee IDs to users and display these IDs in Tempo reports?

[Kerry Kenneally]

We use Jira Cloud for work management. We currently use Tempo for time tracking purposes. Finance wants to associate all of our Jira users with their respective internal Employee IDs and then display these IDs in our Tempo timesheet reports.

I've investigated manually updating users' properties via User Management > Edit User Properties > then adding a key = "Employee ID" and value = "$EMPLOYEEIDVALUE" however, I do not have any way to tie this into Tempo and export. 

This seems technically possible in Tempo but only for Jira DC, not cloud. Does anyone know of a reasonable solution for this? I've looked in the Atlassian Marketplace but am unsure if the two available options out there are viable solutions.

Again, tl;dr: I want to assign unique internal IDs to our Jira users and then have those IDs show in our Tempo reporting.

[James Coller]

Have you tried configuring the Employee ID as a custom Jira field? 

Tempo allows you to configure adding custom Jira fields into data exports of your time logs. In this case, you can have a Jira Field with the Employee ID, add that field to the data export (Tempo > Settings > Custom Fields > Enable Export > Select your Jira Field) and now it will be included in the raw data export. 

You can still create a custom Tempo report based on your filtering choices, and then just export the raw data instead of an excel/csv/pdf by going to the report and choosing Export > Download Raw Data. 

[Kerry Kenneally]

Are custom fields even configurable for user profiles, though? To my knowledge, custom fields are only configurable for Jira issues/screens. 

[David Nickell]

I can't speak to Tempo reports per se, but the data ends up in the Worklogs of an issue;  the worklogs have authors which map to Jira users (I believe).   I did a lot of time reporting for a client last year using the REST APIs and PowerBI.   They used Tempo as well.  

I can build a similar solution for you that relies on your free API;  we can export the data into power BI for reporting and/or dump it straight into excel for manipulation.  

Let me know if you'd like to strike up a conversation.  We can actually do a proof of concept in an hour or two.  Dnickell@splitdimedata.com

[Shawn Stevens]

In my situation and I think the original question was about getting Employee ID into Atlassian and being able to leverage that in Tempo reporting. 

I get that Atlassian has account id (atlassian value), email address (atlassian value) but that doesn't map to our Internal Employee ID that is coming from an external source like say Sales Force or Success Factors. 

Our Okta Integration does have that information but Employee ID was not getting sent to Atlassian Guard as one of the accepted fields, and until we used the Okta Importer, we were unable to get the Employee ID. 

That has been my experience, so definitely looking for more information around what options we have. 

[David Nickell]

Thanks for the clarification.

[Shawn Stevens]

I'm currently also looking to do this. With our setup and our user information being controlled by OKTA talking to Atlassian Guard on our enterprise setup. We purchased the OKTA Importer for JSM Assets. Which then populates a Schema in JSM Assets for us, which includes the Employee ID. 

You can then create a custom field that would then link out to the JSM Assets schema and Employee ID. At that point I believe it would then be a field that is available to include in Tempo reports as a custom field. 

Not an answer but also going down a path to try and get Employee ID from an external source. Still working to validate if this will actually work for me. 

Definitely curious to see what solutions Tempo has for this. 

[Kerry Kenneally]

@Susanne Götz _Tempo_ I saw that you answered a similar question about this (but the use case was for Jira DC, not cloud). Do you have any insight on this?

[Kerry Kenneally]

tagging @Susan Wu on this as well - Susan, maybe you can be of help here?

[Susan Wu]

Hi @Kerry Kenneally ,

Tempo currently cannot include user properties in the export report. A possible work around is to add employee ID of the assignee as a custom field in the work item to include in Tempo Export.

Best regards,
Susan Wu
Tempo Product Expert

[Kerry Kenneally]

Unfortunately that just won't work for us. It'd be incredibly awkward to have a unique employee ID as a custom field within the issue, just for the sake of being able to export it. Ultimately, the use case we need is one where we're able to directly associate users with their employee IDs within Tempo itself or within Jira and have that be read by Tempo.