Dashboard > GreenHopper JIRA > ... > Archive > GreenHopper 2.5 release notes

    PLUGIN HOME      DOCUMENTATION      DOWNLOADS      FAQ & SUPPORT      PARTNERS  


All release notes
GreenHopper 2.5 release notes
GreenHopper 2.5 now considers an issue as done if this issue is in the Done colunm of the TaskBoard and not if this one is associated with a resolution like before so you might experience some changes in the charts based on custom fields (Burnup - Burndown - Value charts). We have also changed the default value of the "Auto-Assign" to false in the TaskBoard. The Auto-Assign to true was not the default behavior of JIRA.


Configurable Summaries and Rows of the List View
In GreenHopper 2.2 we have introduced the configurable cards. We are now introducing the configurable summaries and list's rows.
In your project's GreenHopper configuration panel you will now be able to select the fields to appear in your different issue views for each issue types.

  • By a simple check in the card itself for the summaries
  • By a drop down selection in your list's rows



Global Card Color Configuration
In the previous GreenHopper versions, all projects had to configure their own set of colors for their issue cards.
You can now configure a custom set of colors to be applied to all projects if these ones do not specify their own set of colors.



Introduction of the Done Definition Based on the Done Column of the TaskBoard
For each column of your TaskBoard you can associate multiple JIRA Statuses AND multiple JIRA Resolutions. Based on your workflow and your TaskBoard mapping, GreenHopper will present to the users the available workflow actions when dragging a card from a column to another. If the workflow screen of your workflow step asks for the "Resolution", users will also be able to select the Resolution to set the issue in.

Important: The TaskBoard column "DONE" is the owner of your Project's "Done Definition". GreenHopper will rely on this definition to burn your values in the charts and to swap issues on version releases.

Warning: Playing with the resolutions can be very hazardous. If you are not comfortable with the JIRA Workflows and Workflow screens, We advise you to leave the resolution settings to "ANY".



We have revamped the transition screens to support the new TaskBoard configuration. If the JIRA workflow screens of the transition steps ask for the resolution, GreenHopper will now provide the resolution drop down directly in the TaskBoard transition screen.
Also, if dragging a card into the Done column GreenHopper will ask the user if he wants to reset the remaining time (finally!).



Done Definition Support
Since we are now supporting the done definition for each projects we have added some quick filters to take advantage of this definition.
You will find in your context's filters and highlights the option to hide the done issues or highlight the not done issues.
We have also added in the version boxes two new statistics.

  1. Done --> Sum of all the issues that are answering the done definition
  2. Not Done --> Sum of all the issues that are NOT answering the done definition
    Note: you will always have access to the project's done definition by a simple click on the "Done:" statistic label.





Enhanced Ranking Support
You can now select a group of issues with the multi-select function (Crtl + left-click) and ranked them as a group within your displayed page.
Also to easy up your issue ranking across pages we have added a page tooltip. When leaving your mouse over a page number, a small popup will appear with all the issues that are displayed in the page.


The GreenHopper ranking field is now editable directly from the standard JIRA issue views; Edit and View.
Of course you will have to add the GreenHopper ranking field in these screens via JIRA - Administration.

Capability to View the Pending Issues of the Master Versions
In GreenHopper you can organize your versions in a hierarchical way with the Master option. Very useful in the case where you have versions split up in multiple sub-versions (or Releases in Sprints).
In the previous versions of GreenHopper, it was difficult to separate the issues pending in the Master version from the issues planned in the sub-versions therefore, in GreenHopper 2.5 we have added the "Pending link" directly into the Masters version boxes that will allow you to quickly see all the issues that are not planned in sub-versions.



Capability to set a maximum of issues for the TaskBoard
You can limit the number of issues to show in the TaskBoard thus limiting resource consumption.
If the number of issues exceeds the specified number, the TaskBoard will ask the user to narrow the number of issues by using filters from the context.
This feature was added to support Public or Open source projects to avoid undesired resource load on the server.






And Much More

  1. Cards directly accessible from the list view by double click
  2. Faster JIRA IFrame.
  3. More Ajax support.
  4. UI Polishing





GreenHopper 2.4.1 Fixed Issues

  • [GHS-408] - Edit Issue permission required by GH but not by Jira
  • [GHS-432] - Project drop down list becomes unordered when GreenHopper is enabled only for certain projects
  • [GHS-433] - Static portlet doesn't render correctly if project has no versions
  • [GHS-435] - Static portlet requires URL encoded fieldName but release notes don't mention this
  • [GHS-446] - Can`t minimize the JIRA Iframe once maximized
  • [GHS-459] - The excel export of the ranking field doesnt render the ranking properly
  • [GHS-466] - Cannot rank sub-task if in different version than parent




© Pyxis Technologies Inc. All rights reserved. GreenPepper® is registered to Pyxis Technologies inc.