[
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426893#comment-15426893
]
Will Berkeley commented on KUDU-1566:
-------------------------------------
+1
I like that not all patches need to be attached to a JIRA, but for those that
are it's very helpful to have automated integration between JIRA and Gerrit.
It's really helpful for the community to have easy visibility into the reviews,
too.
We'll have to figure out what the right triggers are for JIRA comments, because
it could become quite verbose if we made a comment for every change in Gerrit.
> 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)
