By the way, it looks like there’s a JIRA plugin that integrates it with GitHub:
- https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin - https://confluence.atlassian.com/display/BITBUCKET/Linking+Bitbucket+and+GitHub+accounts+to+JIRA It does the automatic linking and shows some additional information <https://marketplace-cdn.atlassian.com/files/images/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin/86ff1a21-44fb-4227-aa4f-44c77aec2c97.png> that might be nice to have for heavy JIRA users. Nick On Sun, Jul 20, 2014 at 12:50 PM, Patrick Wendell <pwend...@gmail.com> wrote: > Yeah it needs to have SPARK-XXX in the title (this is the format we > request already). It just works with small synchronization script I > wrote that we run every five minutes on Jeknins that uses the Github > and Jenkins API: > > > https://github.com/apache/spark/commit/49e472744951d875627d78b0d6e93cd139232929 > > - Patrick > > On Sun, Jul 20, 2014 at 8:06 AM, Nicholas Chammas > <nicholas.cham...@gmail.com> wrote: > > That's pretty neat. > > > > How does it work? Do we just need to put the issue ID (e.g. SPARK-1234) > > anywhere in the pull request? > > > > Nick > > > > > > On Sat, Jul 19, 2014 at 11:10 PM, Patrick Wendell <pwend...@gmail.com> > > wrote: > > > >> Just a small note, today I committed a tool that will automatically > >> mirror pull requests to JIRA issues, so contributors will no longer > >> have to manually post a pull request on the JIRA when they make one. > >> > >> It will create a "link" on the JIRA and also make a comment to trigger > >> an e-mail to people watching. > >> > >> This should make some things easier, such as avoiding accidental > >> duplicate effort on the same JIRA. > >> > >> - Patrick > >> >
