Introduce a setting where an administrator can decide whether or not Tempo is automatically set as the time tracking provider upon update of the plugin
Tempo Products | Tempo Timesheets, Tempo Planner, Cost Tracker for Tempo Timesheets |
Tempo Platform | Cloud |
After every update the time tracking settings are overridden. This should not be the case.
It overrides our Jira settings affecting our teams. Please fix this
This issue is affecting our organization. We have Tempo rolled out for a time tracking pilot for a few teams, but the rest of our users continue to use the default Jira worklog functionality. Each time a Tempo update is deployed to the Atlassian Cloud, our global time tracking setting reverts to use Tempo. We are planning to roll out a ScriptRunner script to detect this setting change, and switch it back. However, a native Tempo solution would be highly preferred. We understand how an initial Tempo install might change this setting, but software updates should not be changing Jira settings.
Yes, please implement this feature.
It is impacting our process.
Thanks.