Jira Process
- James Friel
Analytics
Jira is complicated, but we try to keep life simple. Here’s how…
Ticket Types
Jira has a variety of ticket types, we try to keep it simple
Ticket Type | What it’s for | Example |
|---|---|---|
Epic | An overarching topic that will likely encompass several tasks and take a significant amount of time to complete | Combining the various RDMP imaging plugins into a unified imaging plugin |
Task | A single piece of work that can be defined with a list of outcomes. This can be new functionality, or maintenance work |
|
Bug | Something is broken and needs fixed, or something it’s working quite right | Poor error throwing etiquette |
Boards
We try to work in year quarters, as it allows for us to plan some milestones and regular aims and goals
You can find them in Jira filled with tickets tagged for that quarter.
Ticket Labelling
We use labels on tickets to help identify them. Most tickets will have a label like “2023Q3” to link it to a specific quarter.
The labels can also be used to identity different types of issues for simple searching
Raising an Issue
Found an issue or want a new feature? Just raise a ticket in Jira.
Let a member of the team know you’ve raised an issue, and if you’re feeling extra generous, add a “triage” label to it for us to know that it needs triaged.