• Type: Suggestion
• Resolution: Unresolved
• Fix Version/s: None
• Component/s: None
• Labels:

  • affects-cloud
  • affects-server
  • audit-log
  • jira_support_feature_request_emea
  • jira_support_feature_request_sf
  • jw-platform
  • pse-request
  • ril
  • service-desk
  • service_enablement

[JSDSERVER-6208] Add events to the audit log in Jira Service Desk

SET Analytics Bot made changes - 18/Apr/2025 4:35 AM

Support reference count

Original: 1

New: 2

Marc Dacanay made changes - 19/Jan/2025 10:39 PM

Labels

Original: affects-cloud affects-server audit-log jira_support_feature_request_emea jira_support_feature_request_sf jw-platform pse-request service-desk service_enablement

New: affects-cloud affects-server audit-log jira_support_feature_request_emea jira_support_feature_request_sf jw-platform pse-request ril service-desk service_enablement

Marc Dacanay made changes - 19/Jan/2025 10:39 PM

Remote Link

New: This issue links to "Internal ticket (Web Link)" [ 981050 ]

Katherine Yabut made changes - 19/Sep/2019 5:56 AM

Workflow

Original: JAC Suggestion Workflow [ 3090627 ]

New: JAC Suggestion Workflow 3 [ 3650184 ]

SET Analytics Bot made changes - 26/Jan/2019 12:33 AM

Support reference count

New: 1

Sergey made changes - 25/Jan/2019 3:58 AM

Description

Original: In Jira instances managed by a team of admins, tracking administrative events should cover all of the impactful activities.     The administration activities which need to be logged include changes to:  * custom field context  * issue type and issue type scheme  * resolution  * global system settings

New: In Jira Service Desk instances managed by a team of admins, tracking administrative events should cover all of the impactful activities.     The administration activities which need to be logged include changes to:  * custom field context  * issue type and issue type scheme  * resolution  * global system settings   * Request types

Sergey made changes - 25/Jan/2019 3:57 AM

Description

Original: This suggestion has been created from JRASERVER-3157 as a separate feature request because many of the activities requested in the original suggestion are already [tracked in the audit log|https://confluence.atlassian.com/adminjiraserver/auditing-in-jira-applications-938847740.html].   We will use all the comments regarding the audit log from the original suggestion, so there is no need to put the same comments, just make sure to vote and watch the issue! We will provide further updates in here.   ---- In Jira instances managed by a team of admins, tracking administrative events should cover all of the impactful activities.     The administration activities which need to be logged include changes to:  * custom field context  * issue type and issue type scheme  * resolution  * global system settings

New: In Jira instances managed by a team of admins, tracking administrative events should cover all of the impactful activities.     The administration activities which need to be logged include changes to:  * custom field context  * issue type and issue type scheme  * resolution  * global system settings

Sergey made changes - 25/Jan/2019 3:56 AM

Key	Original: JRASERVER-68752	New: JSDSERVER-6208
Project	Original: JIRA Server (including JIRA Core) [ 10240 ]	New: JIRA Service Desk Server [ 15611 ]

Sergey made changes - 25/Jan/2019 3:56 AM

Reporter

Original: Kasia Derenda [ kderenda@atlassian.com ]

New: Sergey [ soslopov ]

Sergey made changes - 25/Jan/2019 3:55 AM

Link

New: This issue is cloned from JRASERVER-68572 [ JRASERVER-68572 ]

Load more older events