How to track administrator-made configuration changes?

[Inna S]

Hi, 

I see that Jira configurations do not maintain 'history of changes'. There are not revisions for configurations of fields, screens, boards, projects, roles and schemes. 

The only place to see these changes are in the Admin audit log that only records the event, but not the difference, 'before' and 'after' states. 

Then there are user related events, that are logged with the generic JIRA user, so for the most sensitive part, we have no idea who has made the change.

So I wanted to create a set of webhooks for these kinds changes and log the events outside of Jira. 

Unfortunately I found there are no webhooks for configuration change events:

https://developer.atlassian.com/server/jira/platform/webhooks/.

They are only available for issues, projects and basic user operations.

How do you go around this problem?

Thank you,

Inna

[Nic Brough -Adaptavist-]

Very simply put. minimise the number of people who can make changes and make sure they are in a team together. 

My standard recommendation is that you should have a Jira project to track all change requests and a team of ideally 2.5, but maybe up to 10 for a very large DC suite.  (The 2.5 is two people with admin rights and a third who has it just in case the two main ones are on holiday/sick/leaving at the same time)

Generally, you shouldn't be trying to automate administrative changes, and there isn't really any need to log them if you've got your administration team working together properly.

[Inna S]

Thank you, @Nic Brough -Adaptavist- 

I won't accept this answer yet, to see if anyone else would want to chime in.