nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Explanation of terminology

Jeremy Wadia

I am a new user to JIRA and wondered if there is a clear explanation of the JIRA terminilogy somewhere?

E.g. What is the difference between …

· Project

· Component

· New Feature

· Task

· Improvement

· Build Updates

· Epic

· Story

Accepted answers

All comments

Penny Wyatt (On Leave to July 2021)

Hopefully these should make things a bit clearer:

http://confluence.atlassian.com/display/JIRA/What+is+a+Project

http://confluence.atlassian.com/display/JIRA/What+is+an+Issue

Jobin Kuruvilla [Adaptavist]

You will find some concepts here.

Jobin Kuruvilla [Adaptavist]

usually its me

Penny Wyatt (On Leave to July 2021)

Ah drat, too slow!

unknown

If you are familiar with other issue trackers then it might help to know that, although the terminology is JIRA specific, there are a lot of concepts that are universal.

For example, the Project in JIRA is pretty much the same as Product in Bugzilla. In Trac (at least the last version I checked) there is no support for multiple projects (or products) so you will not find that term there. Projects are a way to divide the issues; an issue belongs to one and only one project.

Issues corresponds to bugs in Bugzilla and tickets in Trac. In all cases it is the element that goes through a work flow.

Since JIRA is used from more then bugs you have different issue types: New Feature,Task, Improvement. This is a way to classify the issues. Epics and stories are concepts from agile development.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

new-to-jsm