1.5 Speak JIRA

Software is made by human beings. And just as people tend to develop different languages as they live apart from each other, their produced software also comes with different labels. Sometimes, these differences are just in nomenclature but then it can also be due to a different architecture. See the table below for a general guide on learning to speak JIRA as you come from ClearQuest:

ClearQuest

JIRA

Comment

Schema Repository

JIRA Database

JIRA does not separate between schema and user database. Both are in the same instance. The schemas in JIRA are accessible through the administration section. The user database could be compared to the project, version and issue base that JIRA entails.

Schema

Set of schemes

JIRA has many schemes for specific configurations such as notification, permissions, field configuration per issue type, workflows, etc. There is an 1-n relationship between schemes and projects. So for example, you could have a set of internal projects that share the same permission scheme but different workflows while one of theses projects shares a workflow scheme with an external project that on the other hand has a different permission scheme.

User Database

Project

Since JIRA keeps schema and issues in the same database, you can define several projects which can all boast different configuration schemes.

Field

Field

The basic concepts of having fields within an issue is the same. Note however, that in JIRA, you can define field configuration schemes that can be applied to many issue types in different projects.

Hook

Workflow action / Custom field

In JIRA, you can configure custom actions at any stage of a workflow. You can do so with a workflow designer and there is no need to write any source code for the major spectrum of possible actions. Custom fields can also be configured from a range of preset types or written in Java.

Record Type

Issue Type

Same concept in both systems.

State

Status

Same concept in both systems.

action

Transition

Same concept in both systems.

Security model

Permission Scheme, Issue Level Security Scheme

Similar concept in both application. The difference being that in JIRA, you define the scheme independently from a project. That enables you to create 1-n relationships between security scheme and projects. Also, you can give permissions to view issue types and perform actions to a specific user, role or group and additionally consider the relationship of the user to the issue (e.g. edit own comments vs. edit all comments)

Last modified on Mar 3, 2014

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.