So we lost the control of who is an admin and who need to be an admin on jira, and we want to control or prevent settings changes.
There's a way to control this situation? How can we get an alert if someone makes a change that affects every project?
Regards
You could use the built-in audit log to monitor changes, the problem is that this tool is very limited.
Please check this app: https://marketplace.atlassian.com/plugins/com.plugenta.jiraauditor/server/overview
It covers 100% of the administrative changes and get total control on what is happening.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I strongly suggest you treat JIRA like any other production system and use a change control process. I use a project in JIRA for it. Many things won't impact multiple projects like adding a value to a select list. This provides two benefits; It provides a way to report on how much work the JIRA admin is doing when management asks (if they haven't they will), and track who asked for what change and when.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have a project, but before I started working anyone was checking who have permissions and for what they need it.
Now I'm trying to do some order.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sometimes I make use of the Audit Log that can be found under Administration / System, at least since Jira 7.1. You can search by username (author) and e.g. Change Summary, i.e. version created. For me it is helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just checked this, but I cannot see for ex. if someone made a change on Issue Attributes, Priorities.
Regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe "Issue Attributes" are not yet considered in the Audit Log, but fields, group and user management, notifications, permissions, projects and workflows are. Maybe more. This is quite useful.
Also very useful is to check, what other global admins have done, by checking the username in the audit log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.