You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Dinesh Bhat (JIRA)" <ji...@apache.org> on 2016/08/18 16:11:21 UTC
[jira] [Updated] (KUDU-1566) JIRA updater script linking a gerrit
patch to JIRA automatically
[ https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Bhat updated KUDU-1566:
------------------------------
Description:
At times, I have found it hard to track a particular JIRA to a gerrit patch and vice versa to gain more context on a submitted change, code review discussions, etc. I am hoping this will bridge the gap between the review system and JIRA tracking.
Currently, all of our commits do not carry JIRA numbers, but this could be applicable to whichever gerrit patch carries one in its commit message. I have come across such scripts before, so spinning one shouldn't be that hard. Though not as fancy as the below link, we could just add a gerritt link to JIRA comment section whenever a change is submitted(or perhaps posted for review).
https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview
was:
At times, I have found it hard to track a particular JIRA to a gerrit patch and vice versa to gain more context on a submitted change, discussions, etc. I am hoping this will bridge the gap between the review system and JIRA tracking.
Currently, all of our commits do not carry JIRA numbers, but this could be applicable to whichever gerrit patch carries one in its commit message. I have come across such scripts before, so spinning one shouldn't be that hard. Though not as fancy as the below link, we could just add a gerritt link to JIRA comment section whenever a change is submitted(or perhaps posted for review).
https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview
> JIRA updater script linking a gerrit patch to JIRA automatically
> ----------------------------------------------------------------
>
> Key: KUDU-1566
> URL: https://issues.apache.org/jira/browse/KUDU-1566
> Project: Kudu
> Issue Type: Task
> Reporter: Dinesh Bhat
> Assignee: Dinesh Bhat
> Priority: Minor
>
> At times, I have found it hard to track a particular JIRA to a gerrit patch and vice versa to gain more context on a submitted change, code review discussions, etc. I am hoping this will bridge the gap between the review system and JIRA tracking.
> Currently, all of our commits do not carry JIRA numbers, but this could be applicable to whichever gerrit patch carries one in its commit message. I have come across such scripts before, so spinning one shouldn't be that hard. Though not as fancy as the below link, we could just add a gerritt link to JIRA comment section whenever a change is submitted(or perhaps posted for review).
> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)