Issue Summary

As expected, every time a new time tracking tool is installed on Jira, the time tracking global settings are automatically changed to set this new tool as the global time tracking tool.

Since June 06, every time the Tempo app runs an auto-update process, it also reinstalls it, automatically changing the global time tracking settings from Jira to Tempo.

This behavior is only noticed if the user has Tempo installed (for X reason) but uses the Jira time tracking feature instead of Tempo.

In those cases, whenever Tempo runs an auto-update, which can be two or more times a week, the global time tracking settings are changed, and users can't use the time tracking feature until a Jira admin reverts the changes.

The audit log during the Tempo app auto-update process.

Steps to Reproduce

1. Select Settings () > Work items.
2. In the sidebar, under WORK ITEM FEATURES, select Time Tracking.
3. You will see that the current time tracking provider is Jira.
   
4. Navigate to Jira home and select Apps > Explore more apps on the top navigation bar.
5. Find and install the app "Timesheets by Tempo".
6. If you go back to the global time tracking settings, you will notice that the time tracking provider was changed to Tempo Timesheets.
    
7. Revert this change, setting Jira back as the time tracking provider.
8. Select Apps > Manage apps on the top navigation bar.
9. Scroll down the page until the bottom, and select the link "Audit Log".
   
10. Monitor the logs (check one per day- can take 3-5 days) until you get the logs related to the "Tempo" app that gets auto-updated.
    
11. The audit log shows a few rows related to the Tempo app being auto-updated, including reinstalling as part of the auto-update process.
12. Open the global time tracking settings.
13. You will see that Tempo was set back as the time tracking provider after the Tempo auto-update process. (We left it set to Jira previously)

Expected Results

• The Tempo auto update process was causing no issues prior to 06 Jun, its auto-update process should not contain an action that reinstalls the app, which results in automatically changing the global time tracking settings.

Actual Results

• Every time Tempo is auto-updated, if your time tracking provider is set to Jira, Tempo will automatically change the global time tracking settings, making itself the new tracking provider.

Workaround

• If Tempo is no longer in use, uninstalling Tempo would be a permanent solution for this issue.
• Revert this change manually. (requires Jira admin privileges) ----- workaround suggested by Tempo support
• Add yourself as a watcher on this bug report page to receive notifications about any updates on this situation.
• Add a comment on this bug report page whenever this issue happens to you.
• Avoid submitting new support requests to Atlassian asking for updates, since all updates will be posted here. For questions related to it, please leave a comment on this bug report.
• If it is heavily impacting you, I'd suggest you submit a new support request with Tempo support (through their own support portal, not through the Atlassian Support portal) every time it happens, requesting updates on when it will be fixed.
• Tempo's support portal: https://tempo-io.atlassian.net/servicedesk/customer/portal/6

Atlassian next actions

• We are in contact with Tempo and will keep updating this bug report daily, or once every two days, until we get an official answer from Tempo.
• Please note that Atlassian can't fix this issue; it's an issue with Tempo's auto-update process. (Neither can we force Tempo to fix this issue)