>We re-indexed the database last night and now certain tickets show up without the workflow actions to close or resolve.
This is a symptom of something being corrupted in database. Workflow information is held in more than one place and they can drift off. The usual culprits are fatal crashes of Jira, forced stops (kill -9) and someone amending data in the database directly.
The integrity checker is capable of fixing these generally, especially the crash related ones. But if it's down to SQL statements, then there could be too much damage for it to repair and you may have to manually repair your data.
>I find that I can use an SQL statement to resolve and close them but they do not disappear from the view screen.
Unless you know precisely what you are doing, *you should not amend Jira data with SQL*. You need to know exactly which tables to update - workflow, jiraissue, histories etc, and you have to have Jira offline while you are doing it, and re-index afterwards.
If you have been doing direct SQL updates, then I'm afraid your data may be too far damaged to fix this problem here. Do you have a recent backup?
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38368_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user
