I’m working on integrating the Tempo API for JIRA to fetch worklog data. I’m trying to use the worklog report feature, but I’m unsure about the correct server configuration.
The API endpoint I’m attempting to use looks like this:
http(s)://[server].[domain]/plugins/servlet/tempo-getWorklog/?dateFrom=2011-01-01&dateTo=2011-01-31&format=xml&diffOnly=false&tempoApiToken=my-token
I’m confused about what values to use for [server] and [domain]. If I’m testing on my local machine, should I use ‘localhost:port’? Or should it be the actual JIRA URL, like ‘jira.mycompany.com’?
I’m using RestClient in my application to make the API request. Any guidance on the correct server configuration would be greatly appreciated. Thanks!
I’ve dealt with similar Tempo API integration challenges before. Here’s what worked for me:
For the [server].[domain] part, use your actual JIRA URL (jira.mycompany.com). This applies even if you’re testing locally - the API calls still need to reach your JIRA instance.
A common pitfall is forgetting to update your firewall rules. Make sure your application’s IP is whitelisted in JIRA’s firewall settings, or you’ll face connection timeouts.
Also, pay attention to authentication. Tempo API tokens are different from JIRA API tokens. Ensure you’re using the correct Tempo-specific token in your requests.
If you’re still having trouble, try using a tool like Postman to test your API calls. It can help isolate whether the issue is with your RestClient implementation or the API configuration itself.
Lastly, don’t forget to handle rate limiting. Tempo API has request limits, so implement appropriate pausing or queuing in your code to avoid hitting these limits during bulk data retrieval.
Based on my experience integrating Tempo API with JIRA, you should use the actual JIRA URL for the [server].[domain] part of the endpoint. So in your case, it would be ‘jira.mycompany.com’. Using ‘localhost:port’ is typically only for when you’re running JIRA locally for development purposes.
Make sure your Tempo API token has the necessary permissions to access worklog data. Also, double-check that the date format in your request matches what Tempo expects (YYYY-MM-DD).
One thing to watch out for: if your JIRA instance uses HTTPS, ensure your API call uses ‘https://’ instead of ‘http://’. This is a common oversight that can lead to connection issues.
Lastly, consider using Tempo’s v3 REST API if you haven’t already. It offers a more robust functionality and better documentation for worklog retrieval.
hey, I’ve used tempo api before. make sure u use the actual jira url for [server].[domain]. so like ‘jira.mycompany.com’ in ur case.
check ur tempo api token has right permissions too. and watch out for https vs http - that tripped me up once.
good luck with the integration!