[
https://issues.apache.org/jira/browse/KUDU-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564651#comment-15564651
]
Dinesh Bhat commented on KUDU-1566:
-----------------------------------
commit 7328ee2394bfab19e3730fd73168cff8efc1d6b7
Author: Dinesh Bhat <[email protected]>
Date: Mon Oct 10 22:16:27 2016 -0700
KUDU-1566: script to automatically update the fields in JIRA issue
This could be used as a post-commit script for every git push
which mentions a specific JIRA ID in its commit message.
It automatically adds the SHA details to the JIRA comment section.
We could also further enhance this to transition a specific JIRA id
to automatically move to 'resolved' state, and perhaps add one gerrit
link once a review is uploaded, etc.
Change-Id: I0d2c719513f51bb10627c1a7ca41a9e56e08e3d2
> 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)
