You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by GitBox <gi...@apache.org> on 2022/07/22 02:33:33 UTC

[GitHub] [incubator-devlake] Startrekzky commented on issue #2535: [Feature][Jira] Allow users to define their own standard issue types and statuses

Startrekzky commented on issue #2535:
URL: https://github.com/apache/incubator-devlake/issues/2535#issuecomment-1192117374

   > If DevLake allows users to define their own standard issue types and statuses, since DevLake doesn't know about these custom issue types and statuses beforehand, I imagine the users would still need to implement metrics/dashboards by themselves? How does DevLake work with those user-defined standard issue types and statuses?
   
   DevLake will provide pre-defined standard issue types/statuses that users can not change. In addition, DevLake allows users to **ADD** new types/statuses. Thus, 
   1. All the pre-built dashboards/charts based on existing standard types/statuses, such as `Requirement lead time` and `No. of Bugs` won't be affected, users don't have to modify these dashboards.
   2. When users want to measure the distribution of issue types/statuses, for instance, `Number or Ratio of different issue types/statuses` and `Mean lead time for issues in different types/statuses`, users don't have to implement dashboards. Pre-built dashboards will do.
   3. However, in some cases, users have to do customized dashboards. For example, to measure the metrics regarding a specific `customized type/status` of issues.


-- 
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: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org