[GitHub] [incubator-devlake] Startrekzky commented on issue #3368: [Feature][Bitbucket] add Bitbucket Issue Tracking transformationRules

[GitBox <gi...@apache.org>]

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

   @hezyin @thenicetgp @yumengwang03 Compared to GitHub's transformation rules
   
   1. BitBucket does not have `priority`, `component` because the BitBucket issue has `priority`, `component` as semantically explicit attributes that do not need to be extracted from the issue labels like GitHub does.
   
   2. BitBucket does not have a `type` configuration because 
      a. BitBucket issue also has a `type` field, so there is no need to extract it from labels like GitHub does.
      b. BitBucket types are only "enhancement", "proposal", "task", "bug", and cannot be customized by users. So by default we transform "enhancement", "proposal" and "task" to REQUIREMENT and "bug" to BUG to save users' time.
   
   3. BitBucket does not have `severity` because BitBucket does not have related fields, so let's put it aside for a while and do it later.
   
   4. BitBucket has "status mapping" because unlike GitHub issues which only have 2 statuses "open" and "closed", BitBucket has a lot more. We can't transform them to the 3 standard issue statuses "TODO", "IN_PROGRESS" and "DONE" on behalf of users. Thus, we add the "status mapping" configuration to let users decide.


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