Skip to content
Tutorials Center
My learning

Topics

Lesson 15 of 29 ยท Jira Basics

Issue attributes, resolutions, components, versions and plugins

Learn the attributes every Jira issue carries, how status differs from resolution, how components and versions organize work, and what popular Marketplace plugins add.

Issues, Issue Types and Workflows showed you the everyday fields. This lesson goes one level deeper into the parts of Jira that confuse newcomers most: why an issue has both a status and a resolution, what a component is for, how versions connect work to releases, and what plugins from the Atlassian Marketplace can add when the built-in features run out.

Jira itself cannot run on this site, so screens are described in words, and the runnable examples are stand-ins: small JavaScript models of the rules. Menu names differ between Jira Cloud and Data Center and between plans, so check your own instance when something looks different.

The attributes every issue has

An issue is a record with fields. Some are required, some are optional, and an administrator can add custom ones.

Attribute What it tells you Notes
Key Unique id such as SHOP-142 (project key plus number) Never changes, except when the issue moves to another project
Summary One-line title Required
Issue type Bug, Task, Story, Epic, Sub-task Decides the workflow and fields
Status Where the issue is in its workflow To Do, In Progress, Done and so on
Resolution Why the issue was closed Empty while the work is open
Priority How urgent Highest to Lowest by default
Reporter and Assignee Who raised it, who owns it now The assignee can be empty
Description Details, steps to reproduce, acceptance criteria Supports rich text
Labels Free-form tags No central list, so spelling drifts
Components Parts of the product Controlled list per project
Affects and Fix versions Where a bug appeared, where it will be fixed Linked to project releases
Due date A deadline Optional
Estimates Story points, or original, remaining and logged time Depends on the project setup
Environment Browser, operating system, server Mostly for bugs
Attachments, links, watchers, votes Supporting material and people Links connect issues (blocks, duplicates, relates to)

All of these are searchable with JQL (see JQL and Filters).

Status and resolution are different things

Status answers "where is it in the process?". Resolution answers "how did it end?". An issue is considered resolved when its resolution is set, even if the status name is different from "Done". The default set of resolutions in Jira Cloud is small:

  • Done: the work was completed.
  • Won't Do: the team decided not to do it.
  • Duplicate: it repeats another issue (link the two).
  • Cannot Reproduce: a bug that could not be seen again by the team.

Older or self-managed instances often have more, such as Fixed, Won't Fix, Incomplete and Deferred. Administrators can add or rename them. Two useful consequences follow:

  • Several different statuses may all be "closed" for the business: "Done", "Rejected" and "Duplicate" can each set a different resolution.
  • A report on "issues resolved this week" counts by resolution, not by the status name. If a workflow moves an issue to a done-like status but forgets to set a resolution, the issue stays unresolved and shows up on filters such as resolution = Unresolved. Many teams therefore set the resolution with a post function on the closing transition (see Workflows, Permissions and Customization).

When an issue is reopened, a post function usually clears the resolution again. Words such as "Reopened", "Pending" or "Deferred" are not resolutions in the default setup; they are examples of statuses an administrator might create.

A model of status and resolution

The stand-in below models a tiny workflow in which the closing transitions set a resolution and reopening clears it. It then answers two questions the way a Jira filter would.

JS Status versus resolution

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Components: slicing the product

A component is a named part of a project, such as "Checkout", "Search" or "Mobile app". Project administrators create them, and each can have a component lead and a default assignee. When a reporter picks the component "Payments", Jira can automatically assign the issue to the payments lead. That makes triage cheaper and gives you a clean way to ask "how many open bugs does Search have?" (component = Search AND resolution = Unresolved).

Components are best for stable structure of the system (a service, a module, a team's area). They are poor for temporary topics, for which labels or epics fit better. Also avoid dozens of components: if people cannot choose between "Backend", "API" and "Server" in two seconds, the list is too fuzzy.

Versions: connecting work to releases

A version (also called a release) represents a deliverable such as 2.4.0. Two fields refer to it:

  • Affects version: the release in which a bug was found.
  • Fix version: the release that will contain the change.

When you release a version in Jira, it records the date and can show unfinished issues so you decide whether to move them to the next one. The release notes and the "Releases" views are built from the fix version field. In a Scrum project, sprints answer "when do we work on it?" while fix versions answer "when do customers get it?". The two do not need to match, because a release may contain the work of several sprints. See Boards, Backlogs and Sprints in Jira for sprints.

The next stand-in builds simple release notes from issue data, the way a Jira release view groups work by fix version.

JS Release notes from fix versions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Plugins and the Marketplace

Jira is extended by apps (the word plugin is still common) from the Atlassian Marketplace. Some are free, many are paid per user, and all run with permissions you grant them. Cloud apps are built on Atlassian's Forge or Connect platforms; Data Center apps are installed on your own server. Popular examples and what they are used for:

App Typical purpose
ScriptRunner Custom scripts, advanced workflow conditions and bulk changes
Tempo Timesheets Detailed time tracking, planning and billing reports
Xray and Zephyr Scale Test case management inside Jira, linked to requirements and bugs
BigPicture Portfolio views, Gantt charts, program planning
JMWE (Jira Misc Workflow Extensions) Extra workflow validators, conditions and post functions
eazyBI Advanced reporting and analytics beyond the built-in charts
Checklists for Jira Lightweight checklists inside issues, handy for definitions of done

Before installing an app, ask four questions:

  1. Can built-in features do it? Automation rules, custom fields and workflows cover a lot.
  2. Who maintains it? Look at the vendor, the number of installs, recent updates and support terms.
  3. What access does it need? Apps can read issue data; review the permissions as you would for any integration.
  4. What does it cost at your size? Prices usually scale with the number of users, and an app you try with ten users may be expensive at five hundred.

Administrators install and manage apps in the site settings. Remember to remove apps nobody uses.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the difference between status and resolution?

    Status shows progress through the workflow. Resolution records why the issue was closed and stays empty while it is open.
  2. 2. Which field tells you the release in which a bug will be corrected?

    Fix version names the release that contains the change; Affects version names where the bug was seen.
  3. 3. A component lead and default assignee are mainly useful for

    When a reporter selects a component, Jira can assign the issue to its default assignee.
  4. 4. You want advanced test case management inside Jira. Which kind of tool fits?

    Test management apps add test cases, executions and traceability to Jira.

Summary

  • Every issue has a key, summary, type, status, resolution, priority, people, estimates and optional fields; most are searchable with JQL.
  • Status is progress, resolution is outcome (Done, Won't Do, Duplicate, Cannot Reproduce and others in older setups); closing transitions should set it.
  • Components slice the product and can route issues; versions link work to releases through the Affects and Fix version fields.
  • Marketplace apps such as ScriptRunner, Tempo, Xray, BigPicture, JMWE, eazyBI and Checklists extend Jira; check built-in options, maintenance, permissions and cost first.

Next: Boards, Backlogs and Sprints in Jira.