There's no feature for a team token and I'm not sure how useful such an implementation would be in the Atlassian context. However, to a service account token, in Atlassian cloud there's no generic user that you can use as a service account that won't cost you a license seat for the purpose of automating certain aspects of Jira. If you want to create a "service account" type of user, it is the same as creating any regular user but using that user for a dedicated purpose. In your scenario, I would suggest
- Creating a Jira user dedicated to a "service account" function
- Generate a personal API token for this account which you can use for your API functions
Subsequently, if you have the domain verified within your Atlassian organization it becomes easier because you can perform the steps above but manage the API token of this "service account" user much better by being able to revoke the token at will. Also, when using such a user, do not use a single token for the multiple functions this account will do. Generate an API token for each function or integration you expect this account user to perform and label the token based on the integration/function name e.g. Integration with Zendesk, Jira Issue extraction API, Fetch Users API, Integration with Freshdesk etc
That way you can easily administer this "service account" and manage all aspects of the operation when new requirements arise and if things go wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.