We all strive for perfection, but sometimes things slip through the cracks. Unfortunately, today is one of those days.
Due to an unexpected bug, we have taken down the Jira 4.4.2 release. As a result, GreenHopper 5.8 is also on hold because it is dependent on Jira 4.4.2. Other versions of Jira are not affected by this issue.
What is the problem?
This bug in Jira 4.4.2 can cause data corruption on high load servers where lots of new issues are being created simultaneously. Details can be found here: JRA-25914
What if I already upgraded to Jira 4.4.2?
For any Jira customer who has already upgraded to Jira 4.4.2, we recommend you restore from a backup of your previous version as soon as possible.
If you are not able to restore from backup, we have identified a temporary workaround
to mitigate further risk. Please contact Atlassian Support
if you need assistance or have any questions.
How will I know when this issue is resolved?
Last updated: Tuesday, October 18, 2011 @ 9:20pm PT