• 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.

      After add-on is installed, sometimes it makes further changes, like creating a custom field. 

      These changes should get recorded in Site audit logs or in market place audit logs, but it does not show up. This makes it difficult to track changes introduced by add-on in site. 

      Having this visibility will make users more confident in using such add-ons.

            [MP-111] Log changes made by Add-ons in JIRA audit logs

            Anusha Rutnam made changes -
            Link New: This issue is related to JRACLOUD-79986 [ JRACLOUD-79986 ]
            pqz made changes -
            Component/s Original: Global Administration - Audit Log [ 62500 ]
            Component/s Original: Ecosystem - Marketplace [ 62392 ]
            Component/s New: DO NOT USE – placeholder for items assigned to previous component strucuture [ 73399 ]
            Component/s New: DO NOT USE – placeholder for items assigned to previous component strucuture [ 73399 ]
            Key Original: JRACLOUD-81508 New: MP-111
            Support reference count Original: 3
            Project Original: Jira Cloud [ 18514 ] New: Atlassian Marketplace [ 22910 ]
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2

            Carol Low added a comment -

            Thank you for your comments and votes on this Suggestion. Here at Atlassian our backlog is informed by multiple sources including jira.atlassian.com and your feedback is important to us.

            This ticket is in "gathering interest" and we will review this along with other backlog items.

            Regards

            Carol 

            PM, Jira Cloud

            Carol Low added a comment - Thank you for your comments and votes on this Suggestion. Here at Atlassian our backlog is informed by multiple sources including jira.atlassian.com and your feedback is important to us. This ticket is in "gathering interest" and we will review this along with other backlog items. Regards Carol  PM, Jira Cloud
            SET Analytics Bot made changes -
            Support reference count New: 1

            Ran Lavi added a comment -

            This is a critical missing functionality.

            The customers are relying on the Jira audit log to reflect the main admin changes done by anybody, including apps. Unfortunately, the audit log simply doesn’t show anything done by the apps.

            This is a huge concern for our customer! And this makes it very hard for them to approve apps for usage. They simply cannot accept the risk of an app that has Jira admin permission, that can do everything in Jira, without ability to monitor it.

            Ran Lavi added a comment - This is a critical missing functionality. The customers are relying on the Jira audit log to reflect the main admin changes done by anybody, including apps. Unfortunately, the audit log simply doesn’t show anything done by the apps. This is a huge concern for our customer! And this makes it very hard for them to approve apps for usage. They simply cannot accept the risk of an app that has Jira admin permission, that can do everything in Jira, without ability to monitor it.
            Harsaranjeet Kaur made changes -
            Link New: This issue relates to JRACLOUD-3157 [ JRACLOUD-3157 ]
            Harsaranjeet Kaur created issue -

              Unassigned Unassigned
              ab6ef5b5ed7f Harsaranjeet Kaur
              Votes:
              10 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: