No, it should happen automatically. *Should* :) This new round of DVCS support has been far from smooth. I blame it on Atlassian being in the DVCS game now with Stash. I don't think its hard to see that they focus their DVCS testing there rather than GitHub.
On Wed, Apr 9, 2014 at 9:46 AM, Sanne Grinovero <sa...@hibernate.org> wrote: > Nice, thanks Steve. > Do I need to change something in project configuration to benefit from > the automatic linking? > > On 9 April 2014 13:37, Steve Ebersole <st...@hibernate.org> wrote: > > Just a heads up that as or tomorrow (April 10) we should see the Jira / > > GitHub issues resolved. The last 2 issues we have been waiting on were > > just resolved: > > > > 1) https://jira.atlassian.com/browse/DCON-391 > > 2) https://jira.atlassian.com/browse/DCON-393 > > > > Essentially this most recent problem has been the synchronization > process. > > Those 2 issues addressed different parts of that. > > > > All-in-all, that should mean: > > > > * Commit info should start synchronizing automatically again > > * We should start to see Pull Requests automatically linked to the Jira > > issue provided the Pull Request refers to the Jira issue key in its > title. > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev@lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
