Jira reference#

Quick reference for Jira fields, statuses, and workflows at SKAO.

Key URLs#

Resource	URL
SKAO Jira	jira.skatelescope.org
GitLab-Jira integration	GitLab documentation

The issue types available depend on the project and team. The types most teams use are:

Type	Description
Epic	Large feature that spans multiple sprints
Story	User-facing functionality
Enabler	Technical work that supports future features (architecture, infrastructure, research, or compliance)
Task	Technical work item
Spike	Time-boxed research or investigation
Improvement	Enhancement to existing functionality
Bug	Defect requiring a fix
Document	Documentation work item

Status	Description
Backlog	Raised but not yet scheduled for work
To Do	Scheduled but not started
In Progress	Actively being worked on
Reviewing	Under code review or testing
Ready for Acceptance	Awaiting Product Owner acceptance
Done	Completed and accepted
Blocked	Cannot proceed due to a dependency or issue
Discarded	Closed without being completed

Use these keywords in commit messages or MR descriptions:

Keyword	Effect
`SKA-123`	Links the commit or MR to the Jira ticket
`Closes SKA-123`	Links, and marks the MR as closing the ticket. The status change is not automatic at SKAO — move the ticket manually.
`Fixes SKA-123`	Same as `Closes`
`Resolves SKA-123`	Same as `Closes`

Include the Jira ticket ID in your branch name:

<jira-id>-<description>

Examples:

ska-123-add-login-feature
ska-456-fix-pipeline-timeout