You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "Startrekzky (via GitHub)" <gi...@apache.org> on 2023/05/09 12:14:53 UTC

[GitHub] [incubator-devlake] Startrekzky commented on issue #5079: [Question][GitHub] What's the right issue type when multiple labels match the same regex?

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

   My thoughts:
   
   1. An issue only has one `type`, "multiples types" is not allowed in most issue tracking tools like Jira, GitLab issues, TAPD, etc.
   2. I can accept an issue having only one or multiple `original_type`, in fact, only GitHub issues may have this situation. The domain layer table issues.original_type equals tool layer jira_issues.`type`, gitlab_issues.`type`, or github_issue_labels, etc. A GitHub issue's type (e.g. #4861) can be saved as a string like `type/docs,type/bugs` as it has two "type/xxx" labels that match the regex: type/docs and type/bug.
   3. However, the value of this #4861 's `type` should be from only one of the standard type values. We can define an order to check if lables match the regex of these values. if a GitHub issues ($4861) has multiple labels, and it first matches 'type/bug', it should be transformed to `type` = 'BUG'. 
   - REQUIREMENT: type/feature-request
   - BUG: type/bug
   - DOCS: type/docs
   I'm fine with the order or using either first/last match, as long as there's only one type.


-- 
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