FECRU is EOS, but JIRA is still looking for it.

[도메인관리자]

It's very annoying that source tab of jira is still looking for FECRU and then it returns following error.

This list may be incomplete, as errors occurred whilst retrieving source from linked applications:

• Request to https://mantech.jira.com/source/ failed: Error in remote call to 'FECRU (mantech.jira.com)' (https://mantech.jira.com/source) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=MCCSKEY-3023, expand=changesets[0:20].revisions[0:29],reviews}, methodType=GET}] : The host did not accept the connection within timeout of 10000 ms

This list of reviews may be incomplete, as errors occurred retrieving data from the following repositories:

• Request to https://mantech.jira.com/source/ failed: Error in remote call to 'FECRU (mantech.jira.com)' (https://mantech.jira.com/source) [AbstractRestCommand{path='rest-service/search-v1/reviews', params={term=MCCSKEY-3023, maxReturn=50}, methodType=GET}] : The host did not accept the connection within timeout of 10000 ms
• Request to https://mantech.jira.com/source/ failed: Error in remote call to 'FECRU (mantech.jira.com)' (https://mantech.jira.com/source) [AbstractRestCommand{path='/rest-service-fe/search-v1/crossRepositoryQuery', params={query=MCCSKEY-3023, expand=changesets[-100:-1]}, methodType=GET}] : The host did not accept the connection within timeout of 10000 ms

[cbenard1]

Hi Administrator Mantech,

This is happening because though FeCru has been End of Life'd the applications are still live and a redirect has been put in place. Here's the bug ticket for the issue: https://jira.atlassian.com/browse/AOD-6862

The only workaround currently is to go into your manage add-ons section and disable the fisheye plugin for JIRA.

The issue will resolve itself in the near future when the applications have been totally removed.

Thanks

Turner