Paul Miles — CLM Glossary Backlog Tracker (Jira-import Excel template)

Tag: S-2026-06-01-paul-clm-glossary-backlog-template Type: own-writing Author(s): Paul Miles (Red Strata) Date of source: 2026-06-01 Date ingested: 2026-06-01 Authority weight: own-writing. Raw file: Excel on disk at C:\Users\pgmil\OneDrive\Documents\_ClaudeWorkspace\01 Taxonomy\CLM_Glossary_Backlog_Tracker_Jira_Import.xlsx.

What it claims

An Excel template for managing the glossary-definition backlog across both squads through their sprints, structured so the Backlog sheet can be saved as CSV and imported into Jira Data Center (System ▸ External System Import ▸ CSV) as Epics and Stories.

Workbook has four sheets: Backlog (one row per Jira issue — the import-ready tracker), Dashboard (auto-counts by Status and by Squad, plus % Done, via COUNTIF/COUNTIFS), Field Guide & Jira Import (column-to-Jira-field mapping and import steps), and Lists (dropdown source values).

The Backlog sheet has 29 columns: Issue Type, Epic Link, Epic Name, Summary, Business Term, Day Tier, Process Area, Squad / Component, Status, Priority, Story Points, Sprint, Definition Owner (Assignee), Reporter, Source Systems, Conflict?, Conflicting Sources / Notes, Proposed Master Definition, Approved Definition, Policy Tag, Process Tag, Regulatory Tag, CDE?, Data Steward, Governed Artefact Link, Approval Date, Due Date, Labels, Description.

Status workflow mirrors the delivery method: Backlog → Harvested → Clustered → Drafted → In Review → Conflict → Approved → Published (the Done state). Data-validation dropdowns are applied to Issue Type, Status, Priority, Day Tier, Squad, Process Area, Conflict and CDE; conditional formatting colours the Status cell (green = Approved/Published, red = Conflict, amber = In Review/Drafted/In Progress, grey = early states). Epics link to Stories via the Epic Link column. Ships with two sample Epics (Day 1 / Squad A, Day 2 / Squad B) and six sample Story rows (PD, Definition of Default, EAD, LTV, Covenant Breach, Watchlist Status) to be deleted before a real import.

Notable quotes

• “Jira Labels cannot contain spaces — use hyphens (e.g. day1, irb).” (Field Guide)
• “Published is the Done state.” (Field Guide)

What’s speculative vs. asserted

• Asserted: the column set, status workflow, dropdowns/formatting, and the Save-as-CSV → Jira CSV import path for Data Center.
• Speculative / to confirm: exact Jira field mapping depends on the client’s Jira configuration (which custom fields exist, board Story Points field, component and sprint names). The Field Guide flags fields that are typically custom and must be created or mapped at import time.

Topics this feeds

• CLM Glossary Acceleration Squad — the backlog tool that operationalises the squad delivery method.

Open questions raised

• Which of the glossary-specific columns become Jira custom fields vs. labels in the client’s instance.
• Whether the client’s Jira workflow statuses exactly match the eight backlog statuses, or need mapping.