JIRA is one of the Project Management tools supported in CloudMunch. For this category of tools, the main entities being gathered are Sprints, Stories, Defects and the appropriate workflows.
JIRA integration configuration consists of the following parts
- Server Endpoint - JIRA Server can be the URL of either the JIRA Online service from Atlassian or a deployed JIRA Server. The base URL for the JIRA server is required along with any relative path (optional) if exists. If JIRA is deployed on-premise, please ensure that the endpoint is accessible externally. [In some cases, there may be more than one server endpoints, depending on if the stories and defects (or risks) are being kept in different JIRA instances]
- Authentication - Credentials (username/password) that has access to the JIRA project that is being configured with permission to access all the information for that project.
- Scope: Metrics can be gathered for one or more JIRA projects individually or be aggregated across all the projects at the JIRA Instance level. Each level has different set of metrics associated with them.
- Customization - If the scope is set to Project level, then JIRA Project customization is required. These details can be gathered from the Project Settings, under Administration and select Edit Fields in the Actions dropdown. On left Nav navigate to Fields->Custom fields. Let's dive into the details of what is expected.
IMPORTANT: CloudMunch requires JIRA project to be based on Scrum Development Template and use the concepts of Fix Versions, Story Points and Rapid Boards.
|Project Name||The name of the project that will use to pull data from. Ensure that the credentials provided can access the project|
|Rapid Board||Board Id to get Kanban details. Navigate to the Boards section and find the Board that is associated with the project being configured. Ensure that the credentials being used is able to access the Board|
|Story Type||The name of the issue type that has been configured to denote a Story. Select Project Settings for the JIRA project being used and navigate to Issue types. Find the Issue type that best represents a Story in your project. If Scrum Software Development Template is used, then this will most likely be Story. [In many cases, Epic and Enhancement may also represent the type “Story”. Story type can have more than one value]|
|Defect type||The name of the issue type that has been configure to denote a Defect. Follow the same steps are the Story type and end the name. If Scrum Software Development Template is used, then this will most likely be Bug. [It can be Defect, Support, or anything depends on the customization. Defect type can be more than one.]|
The name of the issue type that has been configure to denote a Risk. Follow the same steps are the Story type and end the name. If Scrum Software Development Template is used, then this will most likely be Risk. [Risk type can also have more than one value]
|Sprint field||The id of the field that represents Sprint in your project. Under Administration section for the project navigate to Fields -> Custom fields. Find the field that corresponds to Sprint and copy the Id.|
|Story points||The id of the field that represents Story Points in your project. In the Administration section for the project navigate to Fields -> Custom fields. Find the field that corresponds to Story points and copy the Id.|
|Defect & Risk Severity||Determine the fields that indicates severity for Defect and Risk. If Scrum Software Development Template is used, the default is Priority. [But Instances of JIRA may have custom values equivalent to priority such as criticality, severity, etc.]|
|Defect & Story Mapping||Reference : JIRA. This indicates mapping of custom names for “Open”, “Closed” as well as other states of defects and stories. For example, An instance of JIRA may have custom names “Open”, “In Progress”, “To Do” for “Open” and “Closed”, “Done” for “Closed” state.|
|Story Closed Status||Determine the value of a Story status that indicates that the Story is closed. Story Closed may have more than one value.|
|Defect Open Status||Determine the value of the Defect status that indicates that the Defect is open. Defect Open status may have more than one value.|
|Fix Version Number||Determine the Release version for the application that CloudMunch needs to get Sprints and related information. It refers to the version of the project, in which, the bugs are resolved. As project will have more than one versions, the right version of the project (in most cases, the latest version of the project) should be identified and configured.|
|Project level Metrics||Description|
|Risks||Total number of risks in a project and their classification like Critical, Major and Minor|
|Defects||Number of open and closed defects at sprint level|
|Defects Inbound Outbound||This will show how many defects were raised and closed based on dates|
|Velocity||This will indicate how stories are being burnt against planned at a sprint level|
|Time||The trend graph would indicate how progress has been made during each sprint and also indicates planned and also projects sprint(s) to complete remaining activities|
|Instance level Metrics||Description (there's a card for each project for these metrics)|
|Defects per story||Ratio of defects to stories. This indicates how much new feature development to fixing bugs is being done|
|Stories closed so far & this week||Number of stories closed for the lifetime and for this week|
|Defects closed so far & this week||Number of defects closed for the lifetime and for this week|
|Estimation on Stories||Total amount of time estimated for all the stories|
|Development Time so far & this week||Amount of time logged into JIRA issues till date and for this week|
|Feature Velocity||Average number of story points being completed|
|Estimation deviation||Percentage of time where logged time is different than estimated|
|Time spent on defects & stories||Amount of time spent on defects and stories|
|Projects with Story points||Compliance metric that capture how many projects use Story points|
|Project with time estimation and logged||Compliance metrics that capture how many projects log time for issues|
|Best project - Completion||Best project on the basis of closure of stories and defects|
|Overall defects and Stories closed this week||Total number of defects and stories closed across all the projects|