Roll Back In-Cloud version
Is it possible to roll back the version of the in cloud server for us to the previous version? The exception thrown when setting the assignee to "unassigned" with the latest version is really causing a serious problem for our company.
Please sign in to leave a comment.
May I kindly ask you to provide me with the exception you got and with the steps to reproduce the issue?
Thank you.
For any issue in our youtrack instance, if we change the assignee to "unassigned" we get an exception report form.
Here is the form information:
Environment details
host: ip-10-172-89-169.us-west-1.compute.internalbase url: http://mcneel.myjetbrains.com/youtrack
version: 5.0.2
build: 7374 [29-Aug-2013 15:58]
java.version: 1.6.0_33
java.vendor: Sun Microsystems Inc.
java.vm.specification.version: 1.0
java.vm.specification.vendor: Sun Microsystems Inc.
java.vm.specification.name: Java Virtual Machine Specification
java.vm.version: 20.8-b03
java.vm.vendor: Sun Microsystems Inc.
java.vm.name: Java HotSpot(TM) Server VM
java.specification.version: 1.6
java.specification.vendor: Sun Microsystems Inc.
java.specification.name: Java Platform API Specification
java.class.version: 50.0
os.name: Linux
os.arch: i386
os.version: 2.6.21.7-2.ec2.v1.2.fc8xen
Max memory: 2 GB (2722955264 bytes)
Free memory: 395 MB (414377512 bytes)
Total memory: 2 GB (2722955264 bytes)
Available processors: 2
Thrown at: Thursday, September 5, 2013 9:21:50 PM MSK
Here are the details...
How does this affect us?
Our processes for moving issues from development to the testing team means switching the State from "open" or "submitted" to "Needs Testing". In addition, the assignee changes from the developer to "Unassigned". Each member of our testing staff searches for issues that need testing that are either assigned to them, or unassigned. Now, they don't see some of the ones that need testing because they remain assigned to a developer - the wrong person to be doing the testing.
Our subversion commit hooks automatically call YouTrack to advance the issue to the next step - this is broken.
And, we can't manually work around this because manual assignment to "Unassigned" throws an error.
Our management team is frustrated because they can't determine the current state of issues, and the testing team can't figure out what they're supposed to do.
I realize we could train people to act differently - but by the time we change everybody's habits, you'll probably get this fixed, and we'll have to train them all again.
Can you please roll us back to 5.0.1 ASAP?
Thank you for details.
We found the cause of the issue, and currently investigate it. It's related to http://youtrack.jetbrains.com/issue/JT-21654 .
Fix'll be included in our nearest update. I'll let you know about the progress.
Downgrade is not the cure in this case, because according to our assumptions it woun't fix the issue.
Thank you.
Thanks