Integrity Checker dies while performing checks:
Check Issue for Relation 'ParentProject'
Check Issue for Relation 'RelatedOSWorkflowEntry'
Check workflow current step entries
Check Jira issues with null status
The rest got through and there were some errors to fix which were successfully fixed. Any idea how to overcome this one?
This is a problem i have seen in all integrity checkers.
I believe this has something to do with timeouts of tomcat and proxy.
You can check each integrity checker options one by one rather than selecting all.
That's what i was doing actually, i was running them one by one.
I was able to get results and fixed error from RelatedOSWorkflowEntry
But still can't do anything for the remaining three.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Proxy timeouts is what was causing issues. Direct connect to JIRA solved the issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First run against the server directly - not via any proxy. This should avoid the timeout.
Additionally, if you're confident you will want to run all the suggested fixes, you can add a "Fix" button to the page with the following bookmarklet:
javascript:(function(){
var myForm = document.getElementsByName('jiraform');
var element = document.createElement("input");
element.setAttribute("type", "submit");
element.setAttribute("value", "Fix");
element.setAttribute("name", "fix");
myForm[0].appendChild(element); })();
While on the Integrity Checker page, activate the bookmarklet (by clicking on it), choose what you want to check and click the new "Fix" button at the bottom of the page.
See https://mreidsma.github.io/bookmarklets/installing.html for how to add bookmarklets to your browser.
EDIT: For reasons best known to Atlassian, the above code macro mangles my code and replaces the first colon ':' with ':'. Please change it back before pasting into your bookmark.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
At one point I got message from RelatedOSWorkflowEntry:
Check Issue for Relation 'RelatedOSWorkflowEntry'
ERROR: RelatedOSWorkflowEntry relation is missing, a OSWorkflowEntry will be created: Issue (ID:433139)
But it couldn't fix it and now can even get up to this message, dies earlier.
This issue with id 433139 seems to be deleted. I can't open it and in DB the entry in jiraissues table are all null except ID and Last Updated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.