Comment History for Banking Teams

Why this matters for banking teams

Banking is a regulated industry where the system of record has to survive the scrutiny of an examiner who arrives years later. Native Jira does not give that durability for comments. An edit overwrites. A deletion vanishes. The activity log notes the event but not the content.

For a bank running production change management, vendor risk, or incident response in Jira, that gap is a SOX and FFIEC finding waiting to happen. Approval comments are the evidence of the control. A control whose evidence can be silently rewritten is not a control an examiner will sign off on.

Comment History gives banking teams the durability native Jira lacks. The comment trail becomes versioned, attributed, exportable, and retained for the multi-year windows banks require. Supervisory questions about who approved a change six months ago, and what the approval said, get a single PDF answer.

Where this fits in a banking environment

SOX ITGC season - per-ticket evidence exports replace the screenshot-and-Slack reconstruction that currently dominates Q4.
Supervisory examinations - FFIEC, OCC, FDIC and PRA requests for change-management evidence are answered from Jira directly, not from reconstructed sources.
Material-event reviews - investigation of past incidents draws on the original comment trail even where comments were later edited.

What “good” looks like

Good is the examiner asking for the approval trail on a sample of production changes and getting a folder of versioned PDFs the same morning. Comment History exists so banking teams can answer that request without reconstruction work and without surprise findings.

What banking teams are dealing with today

SOX IT general controls walkthroughs sample change-management tickets - native Jira cannot reproduce the approval comment as it existed before the auditor's review date.
FFIEC IT Handbook expects durable audit trails on change-management and incident workflows - native Jira comment edits overwrite the record.
OCC, FDIC and PRA supervisory reviews ask for written approvals on production changes; an edited approval comment is not durable evidence.
Vendor-risk-management tickets often run for years - retention of the approval comment trail for that long is not native to Jira.
Material-event investigations may need to reconstruct who said what on a ticket six months ago, with no native means to do it.
Three-lines-of-defense assurance reviews flag 'lack of immutable record' on Jira tickets as a recurring finding.

How Comment History helps banking teams

SOX-grade versioned trail

Every comment edit produces a new version with author, timestamp, and content. The trail supports ITGC walkthroughs by giving auditors a reproducible record of approvals and risk reviews.

Long-retention approval evidence

Vendor-risk and material-change tickets need approval evidence retained for years. Comment History retains the comment trail independently of Jira's live comment lifecycle.

Examiner-ready per-ticket export

Per-ticket PDF or CSV exports of the versioned comment trail - drop straight into supervisory-request responses without manual reconstruction.

Point-in-time approval reconstruction

Reproduce the state of approval comments on a change ticket as of any historical date - useful for material-event investigations and supervisory follow-up.

Internal-comment visibility attribution

Banks routinely restrict comments for confidentiality. When a comment's visibility scope is changed, Comment History records the user, timestamp, and before/after state.

Use cases

SOX Q4 ITGC sample of production changes. External auditor pulls 30 production-change tickets. Comment History exports the versioned approval and risk-review trail per ticket as PDF - including any edits to the original approval text.
FFIEC examination walkthrough. FFIEC examiner walks through the change-management control on a quarter of releases. Each release ticket's comment history is exportable in seconds, with full attribution.
Material-event root cause investigation. Bank investigates a material operational event eight months after the fact. Comment History shows the original incident-handling comments on the relevant tickets, even where comments were later edited or deleted.
Annual vendor-risk re-review. Vendor-risk team re-reviews a critical supplier three years after onboarding. The original due-diligence approval comments are preserved in Comment History with attribution.

Common questions from banking teams

Does Comment History support SOX IT general controls?

Yes. SOX ITGC walkthroughs of change management and access management routinely sample Jira tickets. Comment History supplies the versioned approval and risk-review trail that auditors expect, including the original text of any edited or deleted comments. It does not by itself certify a control - but it removes the evidence-reconstruction work that ITGC walkthroughs currently require.

Will Comment History help with FFIEC, OCC, FDIC or PRA examinations?

Yes. All four expect durable audit trails on change-management, incident, and vendor-risk workflows. Where those workflows run in Jira, native Jira does not give examiners the comment-trail durability they ask for. Comment History supplies it - and per-ticket exports drop directly into supervisory-request response packages.

How long can we retain the comment trail?

Comment History stores its data in its own tables (Data Center) or Cloud store, independent of Jira's live data. Retention is configurable up to indefinite. Many banking customers retain for seven years to align with record-keeping rules; some choose to retain indefinitely and use legal-hold workflows for purging.

What about confidential comments inside the bank?

Banks routinely restrict Jira comments to internal-only or specific groups. Comment History tracks visibility-scope changes with attribution, so the audit question 'who removed the restriction on this comment' is always answerable. The Comment History store itself respects the same visibility controls when displaying historical versions.

Try Comment History for your team

Comment History works for banking teams on Jira Cloud and Data Center. Install from the Atlassian Marketplace, or read the main Comment History page for the full feature list.

Try Comment History on the Atlassian Marketplace ↗ See the full Comment History overview →

Also built for

Comment History solves a different problem for each team: