You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by "batjko (via GitHub)" <gi...@apache.org> on 2023/07/26 17:55:31 UTC

[GitHub] [incubator-devlake] batjko opened a new issue, #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

batjko opened a new issue, #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760

   ### 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
   
   When going through my data scope for the Giltab connection, and trying to add a transformation to any of the Gitlab repositories, I only ever get the CI/CD Transformation option.
   I can only assume that's a limitation of the connector at the moment, because I do also have issue tracking among my selected scopes, so I would expect this to show up.
   
   So I would like to also add transformations for Giltab _issues_ on those projects.
   
   ### Description
   
   E.g. currently, when I select transformation for any Gitlab repositories, I see only this:
   
   ![image](https://github.com/apache/incubator-devlake/assets/7287076/61cee941-09a6-4c19-9da9-066815666679)
   
   
   However, as per documentation, I would like to also apply issue transformations, so I would assume this:
   
   ![image](https://github.com/apache/incubator-devlake/assets/7287076/4091f905-d55a-4d37-885d-8b74d2acba6e)
   
   
   
   
   
   ### 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: commits-unsubscribe@devlake.apache.org.apache.org

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


[GitHub] [incubator-devlake] abeizn commented on issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

Posted by "abeizn (via GitHub)" <gi...@apache.org>.
abeizn commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1652812474

   @Startrekzky @yumengwang03 Can you take a look?


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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "clement-igonet (via GitHub)" <gi...@apache.org>.
clement-igonet commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1874577071

   So, could we re-open the current topic ?


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

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


[GitHub] [incubator-devlake] batjko commented on issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

Posted by "batjko (via GitHub)" <gi...@apache.org>.
batjko commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1690649814

   @Startrekzky I'm not using any non-default issue types (we haven't set any up), so just whatever comes up when people click "Create" by default.
   
   I don't specifically need any transform yet, so I have not defined any. Issues for us are just a requirement that all development start from and we don't have any convention for differentiating bugs from stories or otherwise. It's all just "Issues" for us.


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

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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1776255244

   This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.


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

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


[GitHub] [incubator-devlake] Startrekzky commented on issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

Posted by "Startrekzky (via GitHub)" <gi...@apache.org>.
Startrekzky commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1685747560

   Hi @batjko , sorry for the late reply. May I ask:
   1. what specific types of GitLab issues do you use?
   2. what's your goal of transforming them to standard types? 
   
   I asked because there's a default `Incident` type in GitLab issues, so the DORA metrics should not have been affected without any issue transformations.


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

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


[GitHub] [incubator-devlake] Startrekzky commented on issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

Posted by "Startrekzky (via GitHub)" <gi...@apache.org>.
Startrekzky commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1691597057

   @batjko DevLake is not hiding anything in the UI. DevLake doesn't support issue-transformation configuration simply because not many users use GitLab issues to manage requirements/feature requests, so we don't find the necessity of doing it. 
   
   On the contrary, DevLake's GitHub plugin provides the issue-transformation configuration based on GitHub's issue labels, as many users use GitHub issues to manage requirements or bugs.
   
   Does it make sense?


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

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


[GitHub] [incubator-devlake] batjko commented on issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint

Posted by "batjko (via GitHub)" <gi...@apache.org>.
batjko commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1652263594

   In fact, I have all entities selected, but I don't get _any_ of the other transformation types, except for CI/CD.
   
   ![image](https://github.com/apache/incubator-devlake/assets/7287076/d7e2eba4-a4f1-4db2-860f-6914a1f9553d)
   


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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1786241322

   This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.


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

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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #5760: [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint
URL: https://github.com/apache/incubator-devlake/issues/5760


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

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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "xiaomingzhang12 (via GitHub)" <gi...@apache.org>.
xiaomingzhang12 commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1873917884

   I tried it out, and in GitLab, data of the 'incident' type can be successfully collected, but the 'type' field in the 'issues' table remains empty. @Startrekzky 
   ![image](https://github.com/apache/incubator-devlake/assets/142298906/306eb763-ba99-4368-88f6-1892fb2f16f4)
   


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

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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "clement-igonet (via GitHub)" <gi...@apache.org>.
clement-igonet commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1873387400

   > Incident that is used to measure DORA metrics is a system issue type in GitLab, unlike Jira issue types or GitHub's issue labels, so it doesn't need to be transformed.
   What are the rule to import gitlab `incident` as devlake `issue` with `type`=`INCIDENT` ?


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

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


Re: [I] [Feature][Gitlab] Support Issue-type transformations in Gitlab Blueprint [incubator-devlake]

Posted by "Startrekzky (via GitHub)" <gi...@apache.org>.
Startrekzky commented on issue #5760:
URL: https://github.com/apache/incubator-devlake/issues/5760#issuecomment-1873682243

   > So, what are the rules to import gitlab `incident` as devlake `issue` with `type`=`INCIDENT` ?
   
   Hi @clement-igonet . DevLake should collect GitLab incidents and covert them to `type = INCIDENT`by default. If the actuall behavior doesn't meet this logic, then there's a bug.


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

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