3. Use

Make a JIRA Issue executable

This feature allows to create a link between a JIRA issue and a Confluence page which contains the executable specification.

How to use it

Prerequisites The JIRA project must be registered to GreenPepper.

1. Select Create a new reference for this issue from the operations available.

• Once you have created a first link with Confluence, the GreenPepper ref. box appears in the issue information.
  7. From there you can:
  - Refresh the list of links.
  - Create a Issue Hierarchy report.
  - Edit a specification.
  - Run a specification.
  - Delete a link.
  
  
  
  
  
• To create another link, click New Reference and repeat steps 2 to 6.
  
  
  

Embedded specification

This feature allows to define executable specifications directly in JIRA issues. From JIRA, you can also run executable specifications.

How to use it

1. Edit an issue.
2. In a wiki style, type your test in the GreenPepper custom field text area.
3. Define the executable specification in respect of the GreenPepper formalism.
4. Once the issue is saved, GreenPepper provides a menu from which you can:
   • Run the specifications
   • View the execution's result

Here is an example of an embedded specification in JIRA:

Bulk reference management

This feature allows the user to manage references for a group of issues using the Bulk Change functionality provided by JIRA. It also allows the user to run all executable specifications referred by a selected group of issues.

How to use it

1. Select the group of issues for which you want to manage the reference.
2. Click the Bulk Change link.
   
   

1. Select the issues you wish to work on.
2. Choose Manage References among the list of operations and click Next.
3. Now, you can:
   • Manage the references of each issue using the Link an issue with a Confluence specification feature.
   • Run all specifications referenced in the issues selected.
   • View or Hide the result of the execution for each issue.
     
     

Issue Hiearchy report

This feature allows the user to manage the references for a group of issues using the Bulk Change functionality provided by JIRA. It also allows the user to run all executable specifications referred by a selected group of issues.

How to use it

There are two ways to produce an Issue Hierarchy report.

I. From the Browse Project page of a specific project

1. In the Reports section, select Issue Hierarchy Report.
   
   
   
   
   
2. Define the parameters and click Next to view the result.
   

   Issue key	Enter the JIRA issue key to specify the issue to report.
   Link type	This is the type of link available in the project. The types of links are defined in the administration panel, more specifically in Global Settings/Issue Linking.
   Include subtasks	A subtask is a type of issue automatically linked to another issue. By default, the subtasks are included in the report.

   
   
   

   
   
   
   

II. From the Issue Detail page

1. Select the JIRA issue you wish to report.
2. In the GreenPepper ref. box, click on Hierarchy Reports.
   
   
   
   
   
3. You now have to select the type of link and choose whether or not to include the subtasks.
4. Finally, click View Hierarchy to view the result.
   

III. Resulting report

Whatever way you choose, the resulting report will be the following:

Version Hierarchy report

This feature allows the user to manage references for a group of issues using the Bulk Change functionality provided by JIRA. It also allows the user to run all executable specifications referred by a selected group of issues.

How to use it

1. From the Browse Project page of a specific project, you can access the Version Hierarchy report from the list of reports.
   
   
   
   
   
2. Define the parameters and click Next to view the result.
   

   Version name	This is a mandatory parameter defining the issues to be contained in the report. You have to select an unreleased version or a released version from the list provided. JIRA will consider the issues for which the fix version field is equal to the selected version.
   Link type	This is the type of link available in the project. The types of links are defined in the administration panel, more specifically in Global Settings/Issue Linking.
   Include subtasks	A subtask is a type of issue automatically linked to another issue. By default, the subtasks are included in the report.
   Show orphans	The orphans are issues without links. By default, the orphans are shown in the report. (Note that an orphan may have a reference to a Confluence specification.)
   Display as	This report offers two views: Organigram or Tree View. (Note that you can modify the view once the report has been produced.)

   
   
   Here is an example of the resulting report: