Jira Image of the Day: Managing Service, API, and Special User Accounts

[#1]

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management, Jira Core
Deployment Type	Jira Cloud, Jira Server, Jira Data Center

What is shown?

An example table to record and track special user accounts and contacts

What can we learn?

We all know configuration changes can negatively impact the Jira application, its users, and other connected applications. To avoid unintended or unexpected consequences, I keep a list of special user accounts, like service accounts, APIs users, third-party apps, connected apps, and any other accounts with direct database access (for Server and Data Center).

The list helps remind me to consider these users when planning large clean up activities, maintenance, and upgrades (in Server and Data Center). After a big activity, the listed contacts should test their connected applications, if impacted. I don’t want to be digging for the correct contact details if there’s an incident or problem to troubleshoot.

I recommend maintaining a similar list of all the “special-use” users in your documentation area. This way you can better communicate upcoming changes and impacts.

---

Back to intro and image list

[Matt Doar _Adaptavist_]

Also very useful if you have a security incident with an integration and need to be able to say which Jira projects may have been affected

[Julie Beltz]

Is there an way to find out what an API token has been used for.  We have a number of service account tokens created and shared.  But then it is honor system for people to update us on exactly how they are using them.  Would be nice to know more than last used date.