Bugs missed by Engineering by Components
Step 1: Configure a data source that isolates issues reported outside the QA and dev teams using the following JQL query: “reporter not in (membersOf(dev-team), (membersOf(qa-team))“. Replace “dev-team” and “qa-team” with the user group names defined in your Jira instance for the development and QA teams, respectively.
Step 2: Choose the ‘Number of Issues’ Metric
Step 3: Opt for ‘Created by Week’ as the Display By Option
Step 4: Select ‘Components’ for Group by
Step 5: Set Display Mode to ‘Cumulative’ for Accumulated Weekly Data Representation (X-axis Item)
Step 6: Activate the Target Section, Opt for ‘Fixed’ Target Type, and Configure Results Evaluation on a Weekly Basis (Aligned with X-axis Items)
Step 7: Set the target level to a value that aligns with your data. In the provided configuration example, it’s set to ‘8’.
Step 8: Define the target as negative by selecting ‘Exceeding is’ as ‘Bad’. This selection causes any chart results that surpass the target to be displayed in red, indicating failure to achieve.
Step 9: Within the ‘More Settings’ section, enable the ‘Warning threshold’. This setting causes results above the threshold yet below the target to be displayed in amber.
Step 10: Enable the ‘Custom Target label’ option and assign a label that clearly denotes the negative target, such as ‘Max’.
Watch the video tutorial at our website:
https://performance-objectives.com/qa-kpi-bugs-missed-engineering/