Jira – Definitions, Version, Resolution

Quality assurance, Devs and SEO teams ready to help your business grow

Jira – Definitions, Version, Resolution

What is JIRA? | What are versions? | What is the JIRA Resolution field? | What is Automatic Linking? | What is the relationship between Issues, Fields & Schemes?

A JIRA project is a collection of issues.

Every issue belongs to a project.

Each project has a name (e.g. Website Issues) and a key (e.g. WEB).

The project key becomes the first part of that project’s issue keys

A project component is a logical grouping of issues within a project. Each project may consist of various components (or none), depending on your organisation’s needs.

For example, a software development project could consist of components called ‘Documentation’, ‘Backend’, ‘Email Subsystem’, ‘GUI’. A website enhancement request system might consist of components called ‘Products’, ‘Contact Us’, etc:.

An issue can belong to zero, one or multiple components within a project.

What are versions?

What is it? A version is a set of features and fixes released together as a single update to your application. Assigning issues to versions helps you plan the order in which new features (stories) for your application will be released to your customers
Can it be customised? It is fully customisable and requires configuration by someone who can provide the version name; version start date; version release date and a description of the contents.

Issues can be assigned a “Found in Version” which is the version where an issue was initially discovered (usually applied to defects or improvements)

Resolved issues can be assigned a “Fix Version” which is the version that will address a previously opened issue.

How does JIRA use this field? JIRA uses this value to generate a Release burndown report which can be used to assess the progress towards release for a particular version.
  1. When an incident is raised in Service Now that requires the development team to provide a fix, the Found in version should be populated with the last released version of the product to the Production environment.
  2. Stories and defects should have a Fix Version assigned to them. This can be done at the release planning session if the release names are known in advance. Any changes to scope will mean that the Fix version is either removed from a particular story/defect for a scope reduction or added to particular story/defect for a scope increase. This information is also automatically recorded and reported in the Release burndown

What is the JIRA Resolution field?

What is it? Resolutions are the way in which an issue can be closed. When a value is selected for this field, the issue is considered closed by JIRA and the issue number will appear with a strikethrough
Can it be customised? Yes. It ships with a default list (shown on the right) but further resolutions can be added.

Never create a resolution of “Not Resolved”

If no resolution value has been set, JIRA will display “Not Resolved” in this field. However if you create a “Not Resolved” resolution entry and subsequently select it, then JIRA will interpret it as setting a valie for the resolution field and will close the issue.

How does JIRA use this field? Setting this value signifies that the issue has been closed.

For stories, it allows calculation of time spent on the story and allows the burndown chart to be updated with the points associated with the story.

For defects/impediments, it allows the calculation of average defect age and can promote discussions to close long standing defects.

Tips 1. Always ensure that a resolution field is set when a workflow transitions to its terminal state, i.e., Resolved or Closed. This can be done automatically as part of the transition.

2. If there is a “Reopen” status, ensure that the transition to this status clears the “Resolution” value so as to continue calculating cycle time etc.

3. If you make a mistake, consult a JIRA admin to correct it, do not try to create another workflow to fix it.


No Comments

Add your comment