Smart commits do not work anymore following upgrade from JIRA 4.4 to JIRA 5.0.5

Following the upgrade to JIRA 5.0.5, smart commits aren't working anymore.

FishEye is of latest available version: 2.7.13.

Instructions have been re-checked exactly as documented in https://confluence.atlassian.com/display/FISHEYE/Using+Smart+Commits

An Application Link is configured between FishEye/Crucible and JIRA

A project link is configured between FishEye/Crucible and JIRA

Smart Commits are enabled in FishEye.

For the heck of it, and as this used to fix it from time to time following an upgrade of JIRA, application links were deleted a re-created.

In Fisheye any CODE-123 will properly show a link to the JIRA project CODE, and in Jira, source properly shows any activities occurring on the CODE repository ; indicating that the links between the two are properly working.

However, smart commits do absolutely nothing in JIRA.

This is a feature used all the time and is normally required for each commit to contain a reference to the JIRA ticket they refer to... Not having them working is a major issue.

Thank you

2 answers

Hi Jean-Yves,

Sometimes it is neccessary to manually edit and remove old properties entries for the applinks in the config.xml. Stop FishEye and remove all but 1 applink property from the properties section. Leave the property for the plugin itself. You'll see it identified with a version="10". (my version was 10, yours may be different.

There is also a KB article we have: https://confluence.atlassian.com/display/FISHKB/java.lang.IllegalStateException+-+ApplicationLink+with+id+%2712345a67-bcd8-9012-efg3-4hij5k6lmn7o%27+not+found

Perhaps this information will help you out.

If not, open a support ticket at http://support.atlassan.com .

Cheers,

Tom Towkach

Atlassian DevTools Support

Hi Jean-Yves,

Sometimes it is neccessary to manually edit and remove old properties entries for the applinks in the config.xml then add them back using the link you posted above.

Stop FishEye and remove all but 1 applink property from the properties section. Leave the property for the plugin itself. You'll see it identified with a version="10". (my version was 10, yours may be different.)

The ones you want, execpt for the plugin itself all look like this <property name="applinks....

Make a backup of your orginal config.xml because if you make a mistake FeCru will not start.

If not, open a support ticket at http://support.atlassan.com .

Cheers,

Tom Towkach

Atlassian DevTools Support

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

20,608 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you