ManikandanandClaude Opus 5.5
ba15a574ab
Snapshot of the working project as of 2026-10-23 (local 2d4d4fc), one commit with no earlier history: the tracked files were de-identified first (synthetic claim ids and patient data only; see Context.md section 7). Credentials, run logs, screenshots, claim reports and client workbooks are gitignored and not included. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# Issue tracker: Jira (EEWA)
|
|
|
|
Issues and specs for this repo live in Jira, project **EEWA** on ecareindia.atlassian.net,
|
|
reached through the Atlassian MCP tools (cloudId `dbc481dd-f4cd-4204-9f15-02f26c6914a1`).
|
|
|
|
## Conventions
|
|
|
|
- Every ticket is a **Subtask** of **EEWA-5 "Charge Validation"** (EEWA-5 is itself a Task, not an
|
|
epic: a Task with parent EEWA-5 is refused as "Please select valid parent issue").
|
|
- Assignee: **Manikandan** (accountId `712020:a3b618bb-f8b4-4105-9f6f-ba5f88b15804`), set at creation.
|
|
- Statuses: To Do → In Progress → Done. Work that starts moves to In Progress; a ticket is closed
|
|
only when the operator says so.
|
|
- **No claim ids, no patient data, no credentials** in titles, descriptions or comments.
|
|
- Summary style: `<module or condition> (<doc row #>: <one line>)`,
|
|
e.g. `injection_admin_code (#20: add 96372 for injection codes)`.
|
|
- A spec is one Subtask whose description holds the spec. Its implementation tickets are separate
|
|
Subtasks of EEWA-5 that mention the spec ticket's key.
|
|
- Labels: when a skill asks for `ready-for-agent`, add the Jira label `ready-for-agent`.
|
|
|
|
## When a skill says "publish to the issue tracker"
|
|
|
|
Create it with `createJiraIssue` (project EEWA, issueTypeName `Subtask`, parent `EEWA-5`,
|
|
assignee as above, label `ready-for-agent`), in dependency order (blockers first).
|
|
|
|
## When a skill says "fetch the relevant ticket"
|
|
|
|
`getJiraIssue` with the key (e.g. `EEWA-21`), including its comments.
|
|
|
|
## Blocking edges
|
|
|
|
Use Jira's native "Blocks" link: `createIssueLink` with type `Blocks`, `inwardIssue` = the
|
|
blocker, `outwardIssue` = the ticket it blocks.
|
|
|
|
## Comments and updates
|
|
|
|
`addCommentToJiraIssue` for notes; `transitionJiraIssue` for status. Never close or edit the
|
|
parent EEWA-5.
|