plane icon indicating copy to clipboard operation
plane copied to clipboard

[feature]: linking git commits to issues

Open unknowntrojan opened this issue 2 years ago • 3 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Summary

In JIRA, whenever a commit containing the issue ID in it's message is pushed (example: "PROJ-1 add service X"), it will appear in the JIRA issue's page, showing a clickable link containing the message and author of the commit that would take you to the commit's page inside the git provider (GitHub, GitLab or Gitea).

Plane would need to either periodically read the git repository or receive a webhook from the git software. It would need to know the URL of the git provider for the clickable commit link and needs to know which git user corresponds to which plane user. This would also allow easier per-user tracking inside Plane.

For the 0.14 milestone, OIDC support is planned. This feature could be integrated so that users inside the git are mapped to users from the identity provider.

Why should this be worked on?

This feature brings plane closer to JIRA's feature set. It also allows more insight into the actual development being done regarding any specific issue.

unknowntrojan avatar Oct 20 '23 13:10 unknowntrojan

Hey @unknowntrojan, thank you for the feature request. We will work on it.

rhea0110 avatar Oct 26 '23 11:10 rhea0110

Linear does this by linking the GItHub PR to the issue. This is achieved by using the same branch name that is suggested by Linear, and using a webhook to identify the GIthub PR through it's branch name. But currently this causes one UX problem: the Linear status (Todo/In Progress/Done etc) is a step behind the actual status of the issue, and eventually requires manually updating the status. This is because Linear can't recognise that a user has created the branch on their local machine, Linear can only rely on the GitHub platform, thus there's a step missing in the workflow

LazyCoder-1506 avatar Oct 29 '23 17:10 LazyCoder-1506

Thank you for the detailed explanation, @LazyCoder-1506. I agree that this issue should be addressed within Plane. As @vamsi is currently working on integrations, I am tagging him to further discuss and explore potential solutions.

vihar avatar Nov 11 '23 18:11 vihar