[JRACLOUD-3157] JIRA Administration Audit trail / notifications - Create and track feature requests for Atlassian products.

XML

Word

Printable

Details

Type: Suggestion
Status: Gathering Interest (View Workflow)
Resolution: Unresolved
Component/s: Global Administration - Audit Log
Labels:

UIS:
114
Support reference count:
242
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Description

NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Atlassian Update – 14 January 2019

Hi everyone,

For Jira Cloud, we have implemented a number of the audit log requests on the original description, including notification schemes and custom fields. While adding additional Jira-specific events to the Jira audit log is not on our roadmap, we will keep this ticket open to announce if new events are added in the future.

For our cloud products broadly, we are working to add a richer set of audit logs to Atlassian Access in order to provide better visibility into administration activities across all of our cloud products. We are focused on addressing ~~ACCESS-577~~, and then expanding into additional insights into Atlassian account changes, app installations, site and billing changes across all the products in use at your organization.

Regards,
Dave Meyer
Atlassian Product Management

Original request description

We have many Jira Administrators - at least one per project.
In a way, this is due to a missing level of administration (~~JRA-3156~~) - but regardless of that fact, its necessary to know which administrator did what & when - we need to have an audit trail of Administrator actions. In some cases, we need to have notifications - or have additional information in existing notifications detail who the administrator was that performed this action.

Currently, the problems we have experienced are:

A user is created, but we dont know by who. Sometimes, we see a user that isnt meant to exist e.g. "testUser" - but we dont know who to contact to get rid of it.
Sometimes the user themselves have a problem logging on, getting access to their project etc - and it would be useful for them to contact the administrator that created their account rather - therefore it would be useful to have this info in an audit trail, so we can find out who it is - or better still, have this information in the email sent out (~~JRA-2555~~)
A default notification scheme is changed - affecting all projects - and we dont know who did it (we want to know who did it so we can ask them not to do that again) (done)
A global custom field is added (usually by mistake) - affecting all projects - and we dont know who did it (We want to know who did it so we can remove it - and ask them not to do that again) (done)
A new issue type is added - affecting all projects - and we dont know who did it (we want to know who did it so we can discuss using an existing issue type - or discuss the addition of a new type so that it makes sense to more projects)
A user we dont know about is given jira-administrator priveledges. Given the fact that this new user may not know very much about how to administer Jira - and they can go on to do the things mentioned above, then we need to know about this. We need to contact the administrator who did it and ask them not to do it again. We need to contact the new jira-administrator and make sure they know what they are doing! (done)
Someone turns unnassigned issues "on" and all of a sudden Project Leads stop getting notifications for new issues on their project. We need to know who did it, so we can break their legs .
Currently in the audit logs of JIRA, it does not cover changes done in the screen scheme section, or screens in JIRA Administration. We are then unable to find out who performed changes there.

These have been the main ones that have bitten us.

Attachments

Issue Links

duplicates

JRACLOUD-2846 Administrative Change

Closed

JRACLOUD-7846 Enterprise level auditing

Closed

has a derivative of

ID-57 Audit logs don't show author of user and group changes after introducing unified administration

Closed

JRACLOUD-59957 Audit logging for non JIRA Administrators

Closed

JRACLOUD-37378 Audit log does not allow to hide non-human changes

Closed

JRACLOUD-39078 Audit Log: Provide Filter by author of the change

Closed

JRACLOUD-41884 Audit log for field configuration changes

Closed

JRACLOUD-42500 Audit log to display add-on modification/installation

Closed

JRACLOUD-42910 As an admin, I want the audit logs to cover screens and the screen schemes so that we audit it

Closed

JRACLOUD-43160 User and Group Management events in JIRA audit log are anonymous

Closed

JRACLOUD-39347 Auditing localication improvements

Gathering Interest

JRACLOUD-40038 Audit log to display time according to user timezone

Gathering Interest

incorporates

JRACLOUD-14229 See history of changes made to a Version

Closed

is detailed by

JRACLOUD-41340 Add indexing event into JIRA audit log

Gathering Interest

is duplicated by

JRACLOUD-31007 User Details - Show Who Created User

Closed

JRACLOUD-35451 Show user creation and updated date in JIRA UI

Closed

JRACLOUD-39078 Audit Log: Provide Filter by author of the change

Closed

JRACLOUD-39079 Audit Log: Integrate Plugin audit log

Closed

JRACLOUD-39715 Add the custom field ID to audit log for changes in a custom field

Closed

JRACLOUD-41654 Audit log for change to Status configuration

Closed

JRACLOUD-41884 Audit log for field configuration changes

Closed

JRACLOUD-41900 Admin Audit Log should include profiling and logging events

Closed

JRACLOUD-42500 Audit log to display add-on modification/installation

Closed

JRACLOUD-42746 Audit log for changes to Resolutions configuration

Closed

JRACLOUD-42910 As an admin, I want the audit logs to cover screens and the screen schemes so that we audit it

Closed

JRACLOUD-42950 Audit Log for Priorities

Closed

JRACLOUD-43264 As an administrator I want to keep track of changes to Custom Field Configuration

Closed

JRACLOUD-44054 Include Add-ons changes information in Audit Log

Closed

JRACLOUD-46216 Change in Resolutions or Priorities does not end up in Audit Log

Closed

JRACLOUD-47542 custom field updated does not reflect in the audit log

Closed

JRACLOUD-66723 Audit log for user management

Closed

JRACLOUD-68981 Include changes to System Configuration in the Audit Logs

Closed

JSWCLOUD-16709 I want to find, in the audit log, JIRA admins who have made changes.

Closed

is related to

CONFCLOUD-3920 Enterprise level auditing

Closed

JRACLOUD-18119 Version creation data to be stored in JiRA DB

Closed

JRACLOUD-29929 Specific permission in Global Permission to grant or restrict administrator editing the default scheme

Closed

JRACLOUD-68981 Include changes to System Configuration in the Audit Logs

Closed

JRASERVER-3157 JIRA Administration Audit trail / notifications

Closed

CLOUD-5704 Make change log available for customers

Closed

JSDCLOUD-4698 Provide an outgoing email logs

Reviewing

relates to

ACCESS-577 Audit log for user management

Closed

PC-7920 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(7 has a derivative of, 1 incorporates, 1 is detailed by, 19 is duplicated by, 7 is related to, 2 relates to, 9 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Nick Minutello

Votes:: 618 Vote for this issue

Watchers:: 407 Start watching this issue

Dates

Created:: 16/Feb/2004 10:05 PM

Updated:: 2 days ago 12:13 AM