Setting Up Issue Management System in DevDynamics

Step by Step guide to setup your Issue Management System in DevDynamics

Issue Management systems are a critical workspace for your engineering teams and provide a lot data to understand their processes. It is important to configure them properly to measure them accurately. We share with you methods to configure them according to your use case.

DevDynamics integrates with a plethora of issue management tools in various environments. You'll find the list configurations for a few of the popular issue management tools.

Configuring your JIRA instance

Step 1: To configure your JIRA instance after successful integration, head to Settings -> Integration -> JIRA

Click-on the JIRA configuration button

Step 2: Configuring JIRA Field Map

JIRA field map is to help user map relevant fields in their JIRA instance which help measure various data points which leads to accurate calculations for more complex metrics

• Velocity: It gives you an option to use original estimate or story point to track velocity.

• Story Point: This field is to be mapped to any field in JIRA which your teams use for Story Points.

• Start Date: This field is to be mapped to any field in JIRA which your teams use for issue Start date.

• Severity: This field is to be mapped to any field in JIRA which your teams use for issue Severity.

• Sprint: This field is to be mapped to any field in JIRA which your teams use for Sprint.

Step 3: Configuring Issue Type Map

Your teams workspace are very complex with plethora of types of tasks that they perform. To bring a structure to these different types of tasks that they perform, we help you categorize them in 3 types Work Item, Bug, and excluded.

Work - An issue or activity that needs to be completed as part of feature development or a customer request.

Bug - A defect in the software that needs to be fixed.

Excluded - An issue which will be excluded (filtered) from all metrics.

• Issue Type list will provide you a list of all the issue types in your JIRA instance that we have pulled through the JIRA integration.

• You can click on Edit Form button and select the Category against each Issue Type from the 3 available options and save.

Step 4: Configuring Status Map

The Lifecycle of any work item in your organization is very complex. Each work item and team could have their own states and statuses for these issues. To help make sense of this processes, we have allowed user to configure the multiple statuses in categories.

• Ideation : JIRA states of issues where the requirements from various teams including non-engineering are still being discussed and firmed up.

• Product Requirement Document : These are states or statuses in your Issue Lifecycle where requirements are properly documented and details added to them.

• UX Design : These are states for teams which have a design team which creates a UX Design for engineering to look towards inspiration to implement. Statuses that represent these states are to be mapped to this category.

• Tech Design : These are states in the issue Life Cycle where the issue has moved into the hands of engineering teams where they design and architect the implementation strategy to meet the output requirements from previous states.

• Development : These are states in the issue Life Cycle where the real development and implementation of the software occurs.

• Quality Assurance : These are states that represent the Code review, Quality assurance , security review, testing etc. occurs on the code output from the previous state.

• Deployment : This is final status category which denotes when the change is finally made available to users.

Step 5 : Configuring Projects

These are Projects within your JIRA instance that you would want us not to track or Projects that entirely used by non-engineering teams, which makes not-useful to measure such projects.

To solve for the above problem we have enabled you to disable and enable tracking for your Projects based on your requirements, by using s simple switch button.