Jira and workflow

Everything is one Jira project, DEF07 ("DEF07 - Exsport"), a classic software project. Every repo's work lives here.

How this page was verified

From the exsport-repos skill and the project's components and fields, current as of 2026-09-15. Jira state is live — read it fresh before you rely on it.

One project, many repos

Unlike INACT (one Jira project per client), Exsport has one project for the whole product. Which repo a ticket targets comes from two signals:

• Component: Backend, Storefront, Admin.
• Summary prefix: [BE], [Storefront], [Admin] on bugs; (BE) / (FE) on requirement stories, which also carry requirement codes like WEB-HP-00020, ME-MM-01110.

One ticket can carry more than one component and span repos; the fix uses the same branch name in each affected repo. Do not clone the ticket per repo. See Working on a ticket.

House rules that bite

• Load the jira-write-work-item skill before any create or edit — it carries the Markdown-not-wiki-markup rule, the never-record-fix-results rule, and the language rule.
• Language is Bahasa Indonesia (English technical terms kept as-is), with the Indonesian bug headings: ## Langkah Reproduksi, ## Hasil yang Diharapkan, ## Hasil Aktual, ## Akar Masalah, ## Usulan Perbaikan.
• Always add a new DEF07 item to the active sprint. Find it with project = DEF07 AND sprint in openSprints(); sprints rotate (~2 weeks, named DEF07 S<n>). Never hardcode the sprint id.
• Never transition a work item's status. Eris moves items himself.
• On Jira, edit the description — do not post comments.
• Priority defaults to Medium; no labels.

No Sentry here

None of the main repos use Sentry (checked 2026-08-28). So the Sentry-sourced work-item rules almost never apply. Never invent a Sentry short ID for an Exsport item.

People

• Backend lead and usual backend assignee: Rhazes Avicenna.
• Set --assignee on a PR and both the commit author and committer to the work item's assignee — see Standards. The PR author on GitHub is always the person whose token opens it.