I am using Crucible + FishEye with Git repository having application links configured to Jira.
I wondered why my JIRA-123 #start Started progress commits won't change the JIRA ticket. But then I discovered
Because Git and Mercurial allow commits to be attributed to users other than those pushing changes to the repository, if your FishEye instance has any DVCS repositories then Smart Commits will be disabled. This is a security measure to prevent privilege escalation. This only occurs when the feature is first initialised, and will not be disabled if new Git or Mercurial repositories are added afterwards.
Q: Is there a somehow doable workaround for this?
I mean another than delete git repository and recreate it, and I bet won't do this.
Fisheye analysis with Crucible code review. (Version 2.7.13 Build:20120517072828 2012-05-17)
Now, it seemed that Crucible integration started working by +review command. Nice. Did not try that first.
Yet, jira is in other server could that be issue?
Eg. "Issue not found" is shown in mouse-hover on link top of JIRA-123 when commit message was "JIRA-123 #start Show starts"
When I click the link in commit message it opens ok, yet no progress is made.
Does the Jira need some configuration for Smart Commits . I was not able to find such a information.
Jira version is (v4.2.4-b591#591)
Have you created an application link between your JIRA instance and your FishEye instance? See https://confluence.atlassian.com/display/FISHEYE/JIRA+Integration+in+FishEye for more details about this.
Hello Atlassian Community! I'm Teresa, the Product Marketing Manager for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs