Your device is offline, and you are viewing the page as it appeared the last time you accessed it on this device. Content may be out-of-date, and links to other pages might not work.
While your project is being developed, whether that's a new site, theme or solution, you'll be working with one of our project managers and a team of developers in Jira.
From the "Projects" drop-down in the top toolbar you can access all of your current projects. Select a project to view all of the issues raised in it.
Raising Issues
All tickets in Jira are known as "issues".
To raise a new issue, press the "Create" button in the top toolbar.
This will launch the Create Issue pop-up.
Project
This drop-down lists all of the projects you have access to. It will be pre-filled with the project you are currently viewing.
Issue Type
We use the following issue types to categorise tickets in Jira. You can change types at any time.
Bug
The software is behaving unexpectedly or contrary to the specification. Bugs are generally raised against a released version of the project and will be fixed in a future release.
Improvement
An improvement to an existing feature that doesn't introduce new functionality. Examples include refactoring code, performance improvements, and adding support for new technologies.
New Feature
New functionality that will be implemented in a future release.
Epic
Epics represent a large pieces of work that may involve multiple teams, projects and products. They will be broken down into smaller stories to be worked on. It's unlikely that you will need to create an epic, but your project manager may use them to organise the project.
Story
Stories are used in agile projects and are a user-orientated way to describe new features and improvements. They are generally used to break epics down into more manageable pieces of work.
Tasks and Sub-Tasks
Tasks and sub-tasks are things that need to be done. We generally use tasks for things that don't affect the codebase (eg writing training material or documentation) and sub-tasks to break down an issue into smaller items that might need to be worked on by different developers.
Summary and Description
The text you add to the summary field is what you'll see in lists of issues and in search results. Make your summary short but meaningful, so everyone can easily see what the ticket is about.
Your description should describe the issue in detail. A good description for a bug would include:
A URL that links to the problem, and perhaps a second that links to a website showing the expected behaviour
Step by step instructions to recreate the problem
One or more screenshots
A description of the expected behaviour
Any other factors, like browser version or the device used
Components
The components drop-down helps us to make sure your issue is assigned to the correct team as quickly as possible. A project will contain multiple components, so tagging your issue correctly helps keep everything organised.
Your project manager will set up your project with all of the components relevant to it.
Priorities and Fix Versions
Issues are assigned a priority, from highest to lowest. Your project manager will work with you to prioritise issues and assign them to relevant fix versions.
