Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature]: linking git commits to issues #2508

Open
1 task done
unknowntrojan opened this issue Oct 20, 2023 · 3 comments
Open
1 task done

[feature]: linking git commits to issues #2508

unknowntrojan opened this issue Oct 20, 2023 · 3 comments
Assignees
Labels
✨feature 🛫plane Sync issues onto Plane

Comments

@unknowntrojan
Copy link

Is there an existing issue for this?

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

@rhea0110 rhea0110 added 🛫plane Sync issues onto Plane ✨feature labels Oct 26, 2023
@rhea0110
Copy link
Contributor

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

@LazyCoder-1506
Copy link

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

@vihar
Copy link
Contributor

vihar commented Nov 11, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨feature 🛫plane Sync issues onto Plane
Projects
None yet
Development

No branches or pull requests

6 participants