Tried to upgrade JIRA recently on our Win Server 2012 VM (db = SQL Server 2008) from v6.4.12 to v7.05, and then after that failed miserably, to v7.09. Attempts to contact Atlassian support since at least last week have also failed miserably. Launching after the upgrade redirects to a long error message like this:
java.lang.RuntimeException: javax.servlet.ServletException: java.lang.NoSuchMethodError: com.atlassian.jira.security.JiraAuthenticationContext.getLoggedInUser()Lcom/atlassian/crowd/embedded/api/User;
...followed by about 200 lines of error details. Can anyone help?
Upgraded Confluence at the same time, from v5.8.13 to v5.9.4 – that upgrade (on the same server but different port) was uneventful. At this point, I'd be happy to return to the last working version of JIRA (v6.4.12)...
I have still not heard a peep out of Atlassian. I even contacted their sales people, hoping they would rattle some cages. Has anyone been able to get through to JIRA support?
Every time I try to create a support ticket, I get a message telling me the site is down. Has Atlassian gone under? (I know they're "down under" but this is getting ridiculous!)
We restored the VM back to an earlier version (with JIRA working at v6.4.12), then tried the upgrade to version 7.1. No errors, but no page, either. Support site is still down, even though Atlassian is spamming me about their wunnerful JIRA upgrade. Restarting VM to see if that makes any difference. It did not...
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs