Problem using GreenHopper on an interactive white board after upgrade to 6.0.4 and JIRA 5.1.5

[David Sutton]

We use GreenHopper with an interactive white board for our daily stand-up meetings (used by 6 teams across the day).

In order to be able to drag the board up and down (ie equivalent to using the right browser scroll bar, or up and down arrows, or page-up and page-down keys) we have installed an extension to firefox called the 'Grab and Drag' add-on. This has worked well for a year or more. But with the latest upgrade of GreenHopper we can no longer grab the rapid-board on empty column space. Instead we can only grab by the small vertical space between columns (see attachment). I don't know how many teams use interactive white boards and guess that we may be in a minority. However our whole engineering organization is impacted by this and perceive the latest update as a retrograde step in this respect. Is there some subtle unintended change to the column rendering that was recently made that might be undone again please? This was working fine in version 5.10.6 before we upgraded.

[AhmadDanial]

Hey there, David.

We believe that you are using the Add On extension Grab and Drag https://addons.mozilla.org/en-US/firefox/addon/grab-and-drag/.It is best to contact the vendor to assit you with this.

Email: grabanddrag@hotmathematician.com

Warm regards,

Danial

[David Sutton]

Danial,

Just to be clear, the Grab and Drag add-on has not changed, it is GreenHopper that has changed. So it doesn't seem appropriate to approach the Grab and Drag team and expect them to install Jira and GreenHopper in order to investigate in what way Atlassian has change the java script and/or rendering of the board. It looks as though empty space on columns has changed to being empty text fields or something. Additionally the Grab and Drag add-on is a free firefox extension whereas we pay Atlassian for support for both Jira and GreenHopper. I know using GreenHopper on an interactive white board may not be a supported configuration, but up until the change between 5.10.6 and 6.0.1 it worked beautifully.

Best Regards,

David