Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-7170

Include Key Result changes in Audit logs for Objectives

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 11.6.0
    • None
    • Strategy - Objectives
    • None
    • 2
    • Severity 3 - Minor
    • No

      Issue Summary

      Currently adding , updating or deleting a Key Result in an Objective, ( using either the old or new OKR experience ) does not create an audit log entry in the audit log of the objective.

      Issue was initially noticed against Program Tier Objectives but may affect objectives in other tiers.

      Steps to Reproduce

      1. Using New Navigation and the new OKT experience, create a new Program Tier Objective (but don't initially set any Key Results)
      2. Make sue this objective is Saved and then review the audit log (from the ... menu) to see what has currently been recorded
      3. In the Objective, click the + icon next to the Key Results section heading and create a key results of any type
      4. After creating the key result, click the save button at the top of the Objective panel. 
      5. Re-open the audit log - there is no new entry in the log that relates to the creating of the Key Result in the objective

      Performing a similar tes using the old OKR experience shows te same issue.

      Suggestion

      Make creating, modification or deletion of Key Results write an entry into the audit log. of the related Objective

       

          Form Name

            [JIRAALIGN-7170] Include Key Result changes in Audit logs for Objectives

            Mike Goitein added a comment -

            I can confirm audit logging is now comprehensive and clear for both parent Objectives as well as child Key Results.

            Mike Goitein added a comment - I can confirm audit logging is now comprehensive and clear for both parent Objectives as well as child Key Results.

            Kyle Clark added a comment -

            Per the matching issue in our internal development system, this issue has been resolved as of version 11.6.0

            Kyle Clark added a comment - Per the matching issue in our internal development system, this issue has been resolved as of version 11.6.0

            Mike Goitein added a comment -

            Thanks for logging this issue.

            Audit Logging is helpful after the fact to allow us to see what happened.

            However, an even more powerful approach would be to add the same permissioning scheme to Objectives and Key Results that exists for the legacy "Success Criteria" module.

            Due to our internal audit finding, we had to move from OKRs to Success Criteria.

            Goal-setting in regulated environments requires both fine-grained permissions up front, in addition to accurate logging on the back end.

            The OKR module, otherwise, designed and built with such great UX and business logic, is missing these two key pieces to allow it to be adequately leveraged in any situation that requires a mature Governance, Risk, and Compliance ("GRC") approach.

            Mike Goitein added a comment - Thanks for logging this issue. Audit Logging is helpful after the fact to allow us to see what happened. However, an even more powerful approach would be to add the same permissioning scheme to Objectives and Key Results that exists for the legacy "Success Criteria" module. Due to our internal audit finding, we had to move from OKRs to Success Criteria. Goal-setting in regulated environments requires both fine-grained permissions up front, in addition to accurate logging on the back end. The OKR module, otherwise, designed and built with such great UX and business logic, is missing these two key pieces to allow it to be adequately leveraged in any situation that requires a mature Governance, Risk, and Compliance ("GRC") approach.

              dgarcia@atlassian.com Denise Garcia
              1b00672850a3 Colin Weaver
              Affected customers:
              9 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: