Connector Improvement: Capture Github Pull Request data from a PR related to a Jira issue
I'd love to be able to link a Github Pull Request to a Jira Issue
-
Official comment
Hi Paul -
This is a really interesting use case and surprisingly one I haven't seen requests for before. Would you be looking for the PR link on the ISSUE table in the Jira connector or the Issue link on the PULL_REQUEST table in the GitHub connector.
Best,
Erin
-
I suppose either would work and I could sort it out on my end, but preferable from my side to have the PR link on the ISSUE table in the Jira connector. Thanks!
-
Hi I am too looking into using the Jira connector for a specific project. I can't seem to find if you support pulling the code changes (branches and commits) from each issue. Based on the erd, i think no? https://docs.google.com/
presentation/d/ . I found this document https://jira.atlassian.com/1UPq2CWnqQpbjLxkTrcWvAekaZ0o0O dzXODTVmUXeGvs/edit#slide=id. g1379aea0489_0_591 browse/JSWCLOUD-16901 that says while it is not exposed in the official API from jira there are some workaround APIs that an be used to grab this data. Is that something you'd consider adding to the Jira Connector? For our purpose we need the data from issue->code link provided by the github connection to jira. re: https://fivetran.com/docs/connectors/applications/jira . -
Also found this which appears to be a duplicate request: https://support.fivetran.com/hc/en-us/community/posts/1500000690922-Connector-Improvement-Jira-connector-should-replicate-Repository-Commit-information
Please sign in to leave a comment.
Comments
4 comments