Skip to content

Ticket history tracking #1009

@jon-nfc

Description

@jon-nfc

Summary

All changes to a ticket to be recorded

Description

Every change to a ticket to be recorded. This will allow for users to know of changes to a ticket and to assist in tracing any changes that may or may not have an effect on their ticket workflow.

User Story

  • As a user I would like every change made to a ticket to be tracked. This will allow for a full audit history of said ticket.

ERP Modules

Outside of core there is no specific ERP modules effected. This is due to the fact that the ticket model is a core feature even though a ticket can be extended to go within any ERP module.

Business Value

Provides an auditable log of all changes to a ticket.

Acceptance Criteria

  • All changes to ticket fields are recorded
  • All changes create a user viewable entry of said change

Dependencies & Impact

Technical Notes

No response

Risks & Mitigations

No response

Testing Strategy

No response

Additional Notes

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    triageTag given to issues/merge requests requiring triaging by the team.

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions