Jira projects and Confluence spaces

Which key to file a ticket under, and where the written-in-Confluence half of our documentation lives.

Jira projects

Key	Project	Covers
AJOMARK	Alma Mobility Marketplaces	The main delivery project — marketplace features and defects
MONE	Mobility One	The M1 platform
AJOC2B	Baana	The consumer-to-business auction site
AJOINFRA	Mobility infrastructure	Platform and infrastructure work
AT	Autotalli	The Autotalli marketplace — its own Java stack, separate from AJOMARK
AJOUX	Mobility UX	Design and UX work

Keys are right; the rest is thin

The keys and products are current as of 2026-09-02, taken from the ai-ops-playbook Jira configuration. What each project’s components, labels, workflow states and issue types are is not written down here — and mostly should not be, since it changes for process reasons rather than technical ones. Add only what an engineer needs to file correctly.

Issue type, components and labels per project are in that same configuration directory, one file per project — and the Jira Assistant skill applies them for you.

Jira or a GitHub issue?

Org policy, from .github/CONTRIBUTING.md:

• Jira is the system of record for product, feature and bug work. Open the ticket before starting anything non-trivial.
• A GitHub issue is for work about a repository itself — CI, repository configuration, GitHub-side behaviour — or to get technical input before you open a Jira ticket.

Put the Jira key in the branch name and the commit subject where it helps: feat/AJOMARK-1234-add-foo, fix(AJOMARK-1234): correct the total.

Confluence

Two spaces matter, and they are not interchangeable.

Space	For
MONE — Mobility One	People, process, ownership, on-call, who to ask, and anything non-engineers maintain themselves. The newer space
ALMA — Alma Ajo Marketplaces	The older, larger space for the marketplace estate: incident reports, runbooks, QA and smoke-test coverage, Netwheels service notes, and AWS conventions

ALMA is where the accumulated operational history lives, so it is the one to search when a question is “has this broken before” or “how does the legacy side actually work”. It is also less current than MONE — treat an old page there as a lead, not an answer.

MONE is where you find out who to ask for an AWS SSO group and how long it takes — that question is the most common reason a new joiner needs it on day one. See Start here.

The reason it is there rather than here is write access, not read access: both are open to any Alma identity, but Confluence is editable by people who do not open pull requests. Where documentation lives has the full split.

Feature specifications also live in Confluence, against a mandatory template that the Confluence Spec Assistant skill fills in.

Two things are not settled

Whether any space besides MONE and ALMA is expected reading, and which of the two owns runbooks going forward. Both hold some today, and ALMA has the incident-response process and the historical incident reports.