Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Fixed
Fix Version/s: 7.10.0
Component/s: System Administration - Audit Logs
Labels:

UIS:
674
Support reference count:
160
Current Status:
Hide

Atlassian Update – 1 June 2018

Hi everyone,

We’re glad to announce that we’ve added new events to the audit log to let you track more activities in Jira with the 7.10 release. As you may have already noticed, 7.10 was released this week, and you can download it here.

With the new events, you can check who:

created a new issue type

enabled/disabled one of the global settings - “Allow unassigned issues”

In addition, as suggested in ~~JSWSERVER-12017~~, we’ve added events for board changes (board created or deleted) and sprints (sprint deleted).

This update meets the original requests made in this suggestion, and I’ll mark it as resolved. We’ll continue to work on the audit log events, tracking any further requests in this suggestion, which already includes changes to custom field contexts, resolutions, and global system settings.

Here’s an article about Auditing in Jira applications, where you can find a complete set of events currently tracked in the Jira audit log.

You can also read about other features in Jira Software 7.10 in the release notes.

Kind regards,
Katarzyna Derenda
Product Manager, Jira Server
Show
Atlassian Update – 1 June 2018 Hi everyone, We’re glad to announce that we’ve added new events to the audit log to let you track more activities in Jira with the 7.10 release. As you may have already noticed, 7.10 was released this week, and you can download it here . With the new events, you can check who: created a new issue type enabled/disabled one of the global settings - “Allow unassigned issues” In addition, as suggested in JSWSERVER-12017 , we’ve added events for board changes (board created or deleted) and sprints (sprint deleted). This update meets the original requests made in this suggestion, and I’ll mark it as resolved. We’ll continue to work on the audit log events, tracking any further requests in this suggestion, which already includes changes to custom field contexts, resolutions, and global system settings. Here’s an article about Auditing in Jira applications , where you can find a complete set of events currently tracked in the Jira audit log. You can also read about other features in Jira Software 7.10 in the release notes . Kind regards, Katarzyna Derenda Product Manager, Jira Server
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

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

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:

(done as of 7.5.0, see example screenshot-1.png) 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~~)
(done) 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 as of 7.10) 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)
(done) 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 as of 7.10) 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 .

These have been the main ones that have bitten us.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

screenshot-1.png
152 kB
08/Nov/2017 11:00 AM

Issue Links

duplicates

JRASERVER-2846 Administrative Change

Closed

JRASERVER-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

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

Closed

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

Closed

JRASERVER-39347 Auditing localication improvements

Closed

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

Closed

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

Closed

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

Closed

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

Closed

JRASERVER-59957 Audit logging for non JIRA Administrators

Closed

JRASERVER-41884 Audit log for field configuration changes

Gathering Interest

JRASERVER-68425 Improve audit log for custom field updated event

Gathering Interest

JRASERVER-68953 User and Group Management events in JIRA audit log are anonymous

Gathering Interest

incorporates

JRASERVER-14229 See history of changes made to a Version

Closed

JRASERVER-19019 Store version history on the "All projects" section

Closed

JRASERVER-19500 Version History should be recorded.

Closed

is detailed by

JRASERVER-41340 Add indexing event into JIRA audit log

Closed

is duplicated by

JRASERVER-8832 additional logging

Closed

JRASERVER-13352 Audit log for configuration changes

Closed

JRASERVER-15760 Notifications on JIRA level configuration events

Closed

JRASERVER-16345 Notification mail while editing a project role

Closed

JRASERVER-31007 User Details - Show Who Created User

Closed

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

Closed

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

Closed

JRASERVER-39079 Audit Log: Integrate Plugin audit log

Closed

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

Closed

JRASERVER-41654 Audit log for change to Status configuration

Closed

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

Closed

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

Closed

JRASERVER-42746 Audit log for changes to Resolutions configuration

Closed

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

Closed

JRASERVER-42950 Audit Log for Priorities

Closed

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

Closed

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

Closed

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

Closed

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

Closed

JRASERVER-41884 Audit log for field configuration changes

Gathering Interest

JRASERVER-65764 Log changes made to Priorities by users in Audit Log

Gathering Interest

JRASERVER-70388 Audit log for change to Status configuration

Gathering Interest

is related to

CONFSERVER-3920 Enterprise level auditing

Closed

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

Closed

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

Closed

relates to

JRACLOUD-3157 JIRA Administration Audit trail / notifications

Closed

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

(9 has a derivative of, 3 incorporates, 1 is detailed by, 22 is duplicated by, 3 is related to, 1 relates to, 33 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Nick Minutello

Votes:: 548 Vote for this issue

Watchers:: 348 Start watching this issue

Dates

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

Updated:: 16/Aug/2022 12:50 AM

Resolved:: 01/Jun/2018 11:41 AM