The recent UI updates have resulted in a number of usability issues with our JIRA/Confluence. Below is a brief description of some of the problems identified to date:
1) when attempting to access JIRA from a tried and true bookmark the resulting page now states that "The login form has moved", and you are forced to click on a login icon to jump to the login page that was previously accessible directly. It would seem prudent to just jump straight to the new login page rather than throw up the 'moved' page.
2) once at the new login page the "Remember me" check box is always checked. If it is unchecked and you login and then later logout and in again you will find this checkbox defaulting to checked again (your preference is not remembered). It would be safer and IMHO preferred if the default was to have the "Remember me" Unchecked by default.
3)The previously available auto linking between our JIRA projects and their associated Wiki pages has been broken. If we try to jump from a JIRA issue within a project to its associated Wiki pages we now get directed to the Wiki Dashboard rather than to the project's wiki page. This can be very irritating, especially considering that it worked perfectly before the update to the UI.
Is there a setting that needs to be implemented so as to return the JIRA/Wiki linkages to their previous linked state?
4)Whilst talking about the Wiki I'll raise a small yet frustrating interface issue. When the Wiki Dashboard contains a long list of pages/links under the "Global Spaces" heading, it will display a line like "Showing 20 of 35 (View all)". If you click the "View all" link it will take you to a new page that will list 24 of the "Global Spaces" followed by links to the 'Next' page. It would make sense for 'view all' to actually display all the spaces on one page.
If there is a setting to address this, it would be appreciated if someone could provide the details.
In a nut shell, the new UI feels to be a step backwards from a usability standpoint. Let's hope that some or all of these issues can be addressed with minimal fuss in a future UI update.
Thanks.