We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      When a capability is split, the audit log for the Part 2 is empty

      Steps to Reproduce

      1. Create a Capability
      2. Split the Capability
      3. Go to the Capability Split part 2
      4. See the Audit log

      Expected Results

      The Audit log should have the information used when the Capability Split Part 2 was created, it should not be empty on both the original capability and the newly created split capability. 

      Actual Results

      The Audit history is empty as it relates to the split for both the original Capability and the newly created one from the split.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 1
              • Severity 2 - Major
              • No

                Issue Summary

                When a capability is split, the audit log for the Part 2 is empty

                Steps to Reproduce

                1. Create a Capability
                2. Split the Capability
                3. Go to the Capability Split part 2
                4. See the Audit log

                Expected Results

                The Audit log should have the information used when the Capability Split Part 2 was created, it should not be empty on both the original capability and the newly created split capability. 

                Actual Results

                The Audit history is empty as it relates to the split for both the original Capability and the newly created one from the split.

                Workaround

                Currently there is no known workaround for this behavior. A workaround will be added here when available

                        kbyrd@atlassian.com Kyle Byrd (Inactive)
                        7b5a6a24aeb0 Allan Silva
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            kbyrd@atlassian.com Kyle Byrd (Inactive)
                            7b5a6a24aeb0 Allan Silva
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: