GreenHopper 5.5 Upgrade Guide

• Users open the JIRA 'Edit Issue' page in an iframe and modify some of the field. They then click the iframe 'Close' action rather than saving the JIRA page within the iframe. As such, the user loses their changes and must once again open the iframe to edit the issue. We have received requests to put the 'Save' and 'Cancel' buttons from within the JIRA page on the iframe itself. Unfortunately this is not possible as GreenHopper does not control the content within the iframe and users can navigate away to another issue altogether.
• Problems occur when page-zooming is used (often on a TV or projector in planning meetings) and the JIRA Iframe 'Close' action is not visible. The minimum screen resolution for JIRA, and therefore GreenHopper, is 1024 x 768 with a maximised browser window. If a user has this minimum resolution and opens the JIRA iframe, then the minimum for JIRA 'View' or 'Edit Issue' page within the iframe is no longer true.
• JIRA 4.2 onwards includes functionality that is not designed and/or tested for use within an iframe. As such GreenHopper can no longer ensure that the page displayed in the iframe will behave as expected.

In GreenHopper 5.3, keyboard shortcuts were introduced to allow quick navigation and issue editing throughout JIRA and GreenHopper. In addition, a user can 'middle-click' on an issue key to access the JIRA View Issue page for that issue in a new tab. With the introduction of keyboard shortcuts and the Operations Dialog in JIRA and GreenHopper, there are far easier and faster ways to work. The Operations dialog allows quick access to many actions that would have previously needed a round-trip to JIRA (in the iframe or directly).