GSoul-hub opened a new issue, #4217: URL: https://github.com/apache/incubator-devlake/issues/4217
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case As a QA lead, I want to be able to compare the Scrum team's efficiency using DORA. ### Description At the moment, devlake allows mapping only issue type (e.g. "Incident" maps to the "Bug" of JIRA issue type). Our current configuration of JIRA: "**Bug sub-task**" (a.k.a. Sprint bug) - a bug is caught during the testing of a new feature (sprint), we can clearly associate it with the feature, so we create it as a sub-task under the feature's main task. "**Bug**" (a.k.a. Regression/Release bug) - a bug is caught during regression testing before release to a production environment. Since it is not unequivocally clear which feature influenced the appearance of this bug - it is registered as a separate issue (not a sub-task). "**Bug** with **JIRA label "production**" - a bug is caught in the production environment (by the team, clients, or customers). As I understand, DORA should include only "production bugs", but devlake configuration supports only issue type and can't be separated by labels. In our cases - regression and production issues will be treated as DORA incidents which will not be correct (shouldn't include regression bugs). We have multiple teams in our company and as a result, changing/agreeing to the jira configuration setup is quite a long process (e.g. introducing separate issue type only for production bugs). ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
