hezyin commented on issue #2535: URL: https://github.com/apache/incubator-devlake/issues/2535#issuecomment-1191863435
@Startrekzky Thanks for the detailed user stories and analysis. I need some help in understanding the benefit of allowing users to define custom standard issue types/statuses. In our old approach, users map their original issue types/statuses to a fixed set of issue types/statuses that DevLake knows of and uses to write SQL queries. The benefit is then users don't need to worry about metric calculation and creating dashboards. The limitation is that users are restricted to the fixed set of issue types/statuses that DevLake provides. 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? -- 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]
