-
OneDev
changed state to 'Closed' 2 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (bbe4327e)
-
OneDev
changed state to 'Released' 2 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3968 is successful
-
This happens as state of some issue is out of sync with state spec. Please upgrade to 8.6.8 which allows to access OneDev, and then switch to Administration / Issue Settings / Check Workflow Integrity to run integrity check to fix potential problems.
-
@robin Thank you for the update. We are now able to login again.
However, when I run the Check Workflow Integrity, and try to delete the state; it states:
OOPS! There Is An Error could not execute statement
-
Is the error page showing more details of the error? If not, please check server log.
-
@crobinson never mind. Turns out this is another bug, which has now been fixed in build #3971
| Type |
Bug
|
| Priority |
Major
|
| Assignee | |
| Affected Versions |
8.6.7
|
| Labels |
No labels
|
Issue Votes (0)
Our org isn't able to use onedev unexpectedly.
Full error below: