To download the latest documentation for the Go2Group DOORS Plugin for JIRA (PDF), simply click on the link below.

Go2Group provides free, fully-supported, 30-day evaluations for the Go2Group DOORS Plugin for JIRA. Once you are ready to begin your evaluation in earnest, simply fill out the Go2Group Contact Form and we'll generate and distribute your evaluation license key.

	JIRA_DOORS_installation.pdf

Go2Group DOORS Plugin for JIRA

JIRA Integration with IBM Rational DOORS

Requirements management and issue tracking are fundamentally related concepts. In a sense, requirements drive almost all issue tracking data -- requirements drive new feature development at the onset of a project, and failure to meet requirements drives bug reports in the test cycle of a project.

This relationship drives a need to make information from one system visible to the other. We want to answer fundamental questions like:

• What new requirement is driving all of these feature requests?
• Was this requirement problematic? How many bugs did it cause?

Unfortunately, requirements managers and issue trackers are often provided by different vendors and do not easily communicate. Moreover, due to restrictive licensing, requirements managers are often
available to only a few users.

JIRA and DOORS are two of the leading products in their respective fields. The DOORS JIRA Connector is a JIRA side plugin that provides several integration features that help share information between these two important systems.

1 Summary of Common Usage and Features

• The DOORs Plugin can be setup with a new JIRA project that has no issues, or an existing JIRA project that already contains issues.
• Once the plugin is installed and configured, you may create new JIRA issues with or without a DOORs requirement attached.
• For existing issues already in the JIRA project that are not related to a DOORs issue, you can Edit the existing JIRA issue and add a DOORs requirement at any time if desired.
• Add new requirements to DOORs at any time and they will be available to their associated JIRA project automatically.
• Linked JIRA issues are displayed in DOORS as hyperlinks in the Comments field.
• Can change any DOORs requirement at any time and it will be reflected in any associated JIRA Issue the next time it is accessed or new JIRA issue is created.
• Can associate one DOORs requirement to one JIRA issue, or any combination: 1 to 1, 1 to m, m to 1, or m to m. 
• The feature of automated 'bulk' pulling of requirements from DOORs allows you to seed your JIRA project with new issues based on the requirements in DOORs. From the JIRA Administration Project console, by clicking 'Import DOORs Requirements', you initiate the 'bulk' pulling process, creating a new JIRA issue for each requirement in DOORs. This operation can apply to new JIRA projects with no issues, or existing JIRA projects that already has issues (no effect on existing issues).
• Once issues are imported into a JIRA project, the door is open to replicating and updating the DOORs custom fields with other custom fields, allowing you to share the requirements with GreenHopper, synapseRT, or into Quality Center (using Go2group's JaM Plugin).

2 Detailed Illustration of Features

2.1 Linking Requirements to Issues

Any JIRA project that is configured to use the plugin (see the Configuration section) will have the DOORS Requirements custom field available. This field is a select list showing all of the requirements available for the associated DOORS project and module (Figure 2). The field allows multiple selections. Use this field to link a JIRA issue to the DOORS requirement that is driving the ticket. 

Figure 2: Requirements field

Once one or more requirements are selected for an issue, the plugin will display additional information
about each requirement, giving JIRA users a quick insight into the requirements driving the activity
(Figure 3). This information is also available as an issue tab panel (Figure 4).

Figure 3: Viewing requirements field

Figure 4: Requirements for an issue

Linked JIRA issues are displayed in DOORS as hyperlinks in the Comments field (Figure 5).

Also displayed is the JIRA ticket's status.

2.2 Searching for Requirements in a JIRA Project

The custom field is available for searching in JIRA (Figure 6). (Note that, since the list of available
requirements varies depending on the JIRA project, you must select a JIRA project in the search
context first.) Searching on this field will tell you which JIRA tickets are tied to any particular
requirement(s) (Figure 7).

Figure 6: DOORS Requirements custom field in Issue Navigator

Figure 7: Searching for all issues linked to a requirement

2.3 Reporting on Issues Linked to a DOORS Project

The plugin contains two project tab panels, available on the Browse Project screen.

The first panel "DOORS Requirements" displays any DOORS requirement linked to any issue in the active JIRA project, as well as a list of any issues linked to that requirement (Figure 8). This feature, although simple, provides valuable information about which requirements are driving activity in a JIRA project. Essentially, for the DOORS project and module associated with the JIRA project, it reports any JIRA activity linked to requirements in that project and module. 

Figure 8: Overview of requirements in one project

The second panel "All DOORS Requirements" displays all DOORS requirement mapped to that JIRA project (Figure 9).
Figure 9: Overview of ALL requirements in DOORS for one project\module

2.4 Importing DOORS data into JIRA

Data from any DOORS module can be imported into any JIRA project. This feature is available on the
Project Administration page, as shown in Figure 10.

Figure 10: Import Requirements link

When the import process is started, you are prompted to enter several pieces of information, as shown
in Figure 11:

• The name of the DOORS project to import from
• The name of the DOORS module to import from
• The type of JIRA issue to create
• The priority of the new issues

 
Figure 11: Input parameters for DOORS import

As we can see, any DOORS module can be used to seed issues into a JIRA project – requirements, test
cases, and so on.
After creating the new issues in JIRA, a summary screen displays a list of the new issues and a count of
the number of issues created (Figure 12). The new issues use the default assignee for the JIRA project,
use the DOORS object heading as the issue summary, and contain a brief comment with other pertinent
data.

Figure 12: Imported data summary

Note:

• you must have Create Issues permission in order to use this feature.
• Running it again will not result in an update, but in all existing issues being copied as new issues into the JIRA project.