Programeter - JIRA Integration

Atlassian's JIRA is a web-based issue-tracking tool widely used as a way to manage bug and task tracking for many large scale open source and public projects.. It also can be used effectively for project management with plugins like GreenHopper. Currently it has over 12,000 users.

There are a few aspects which make JIRA stand out of other similar tools. First of all, it can be used for nearly everything throughout the development lifecycle. JIRA suits well for requirements gathering, task management, bugs tracking, features tracking and more.

From a project management perspective, the tool gives a good view over the whole team - its easy to track the tasks assigned to a single person, team, or project. From user’s point of view JIRA is well suited to non-technical users as it uses intuitive concepts and user interface.

Facts about JIRA
  • JIRA is developed by Atlassian 
  • It is popular for providing free licences to open source projects
  • 1.0 was released back in April, 2002

Integrating Your JIRA Data With Programeter

Programeter monitors JIRA and automatically generates reports about trends on projects scope and quality assurance metrics. It also combines metrics from JIRA with metrics gathered from the code repository. Resulting reports help to track software project status in completely automated way.

In order to add JIRA to your Programeter project, click "add BUG system" (if JIRA used for bug tracking) button or "add Task system" (if JIRA used for task tracking) and integration dialog box will show up. Bellow you will find instructions how to add JIRA as bug tracking system to your Programeter project.

Step 1: Choose JIRA
From drop-down menu choose "JIRA".

Step 2: Add URL, username and password
The URL is IP or web address of your JIRA server with a path to the project. In order to scan your project's JIRA, Programeter also needs a read-only user account. The username and password settings should be configured accordingly.

Step 3a: Add name and define bug types (optional)
This step is required if you are using JIRA as a bug tracking system.

Add Name for your JIRA bug system at the bottom. Then choose Bug Types from drop-down menu. Bug Types is comma separated list of ticket types that correspond to bugs. By default JIRA configures it as "defect".


Step 3b: Add name and define tasks types (optional)

 Follow this step if you are using JIRA as a task management system. Dialog box looks similar as from step 3a, except last field is for Tasks types and not Bug Types.

Add Name for your JIRA bug system at the bottom. Then choose Task Types from drop-down menu. Task Types is comma separated list of ticket types that correspond to tasks. By default JIRA configures it as "enhancement, task".

Step 4: Verify integration status
Status of your bug tracking tool integration is set to "configured". Initial scanning and analysis is resource consuming process and can take in certain cases up to few days, so please be patient. Status will be changed to "monitoring" meaning, now you can access reports for your project. If the status is marked "error", please contact our helpdesk.

Reports based on JIRA Data scan

Programeter has three types of reports which rely on data pulled from JIRA. Firstly, there is a report on completed tasks and bugs (belongs to Effort angle) which shows the correlation between completed tasks and fixed bugs.

Secondly, features burn-up and tasks statuses reports from Scope angle. These reports display how project scope is changing through the lifetime of the project. They also are used to evaluate task execution effectiveness.


             
Thirdly, bugs statuses and product quality reports from Quality Assurance angle. These reports indicate the effectiveness of bug handling and the correlation between the number of total completed tasks and total bugs through the project timeline:
           

If you would like to take a look at other charts generated by Programeter, please take a look to product page.
Olark Livehelp