In September, Atlassian rolled out Atlassian Service Accounts for Jira Cloud. This lets you create jira-native service accounts where you can generate oauth or access tokens and grant the token/service account admin permissions. Tempo should support the use of Atlassian service accounts for automation so it is tied to a service account and not an individual user who may leave an org.
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
In the same way, we see that the same problem is solved in Xray plugin, which we are also using. Auth2.0 clientId and secretId can be generated for service accounts in the Jira Administration section, so it is something that should be technically possible.
I suppose it is a crucial feature because using service accounts instead of personal users is a well-known best practice. Especially considering the hapenning/upcomming massive migration from Jira DC to Jira Cloud.
Any plans related to implementing this feature? Could the priority be raised somehow?
I also vote for this too.