Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].


2013 年 5 月 30 日

The Atlassian team announces the release of GreenHopper 6.2.2, bringing you:

This release also includes a number of fixes.

Upgrading to GreenHopper 6.2.2 is free for all customers with an active GreenHopper license.

If you are using GreenHopper "behind-the-firewall" (that is, if GreenHopper is installed on-premises at your site), you can upgrade via the JIRA Plugin Manager. Before upgrading, please read the GreenHopper 6.2 Upgrade Notes. Please note that GreenHopper 6.2.2 is only compatible with JIRA 5.1.x and higher.

If you are using GreenHopper OnDemand, please watch the GreenHopper OnDemand Release Summary for the latest updates.

 


Export to Excel in a single click

You can now export your selected issue(s) from Plan mode instantly. Simply right-click and choose View in Excel:

All fields will be exported.

(info) Note: Due to technical considerations, the length of the URL that can be exported is limited to 2048 characters. This may limit the number of issues that can be exported.


^top


Epics integrated into JIRA

For your convenience, JIRA is now more epic-aware:

Associate a story with an Epic, from within JIRA
You can now use the Epic Link field to add an issue to an epic directly from the issue or story in JIRA, when creating or editing an issue via the JIRA Create/Edit popup:

(tick) Click Configure Fields to add the Epic Link field to your JIRA Create/Edit popup.

^top

Move a story to different Epic from within JIRA

The Epic Link field is also editable when using the JIRA full editing screen. Type-ahead is included for your convenience:

^top

Add a story to an empty Epic from within JIRA

The "+" icon now appears in the Issues in Epic area, even if an epic doesn't yet contain any issues:

^top

The Epic Link field now shows the epic's name in your JIRA Issue Navigator

If you add the Epic Link field as a column in your JIRA Issue Navigator, it will now display the actual name of the epic (rather than the issue key of the epic).

Additionally, if you export via JIRA, the Epic Link field will be included in your Excel export — so you can create an export that contains the Epic Link field, but not necessaily all issue fields.

^top

Autocomplete for Epic Link in JQL

When you search on the "Epic Link" field, the values on the right hand side are now auto-completed. This allows you to more easily search for issues which belong to a particular epic, e.g. start typing "Epic Link" = Mo to see all the epic names that start with "Mo":

^top

French, German, Japanese and Spanish Translations

As part of our ongoing efforts to better serve our customers around the world, we are happy to announce that German, French, Spanish and Japanese translations are now bundled with GreenHopper. Simply change your preferred language in your JIRA user profile (see the JIRA documentation on Managing your User Profile).

They are also available from our Translations site, https://translations.atlassian.com/

^top

Updates and Fixes in this release

GreenHopper 6.2.2 includes the following updates and bug fixes:

T キー 要約
Refresh

^top

 

 

12 Comments

  1. Christen Lorensen

    May 29, 2013

    Warning: This upgrade just broke our Greenhopper installation. The plugin has just been disabled, and we cant enable it again

    1. MattS

      May 29, 2013

      If your memory was low then anything could have broken JIRA, not just updating GH

      1. Christen Lorensen

        May 30, 2013

        Well nothing else broke it, so it seems that the new version is useing more memory? And it should be written in the upgrade notes that this is the case, and you might need to increase it?

        1. Rosie Jameson [Atlassian]

          May 31, 2013

          Can you please contact http://support.atlassian.com for investigation and assistance? Many thanks

          1. Christen Lorensen

            Jun 04, 2013

            I already had, which I wrote in a comment here. Why is it that I get the feeling you (Atlassian staff) don't read through comments and issue descriptions before you comment (or close issues)? (It is not the first time, this has happened for me.)

            1. Rosie Jameson [Atlassian]

              Jun 17, 2013

              We do our best. There is quite a large volume of comments to respond to. Apologies for any inconvenience.

  2. Kevin Shine

    May 29, 2013

    New version of GH needs JIRA 5.1 and up

  3. Christen Lorensen

    May 29, 2013

    running: 5.2.1: https://support.atlassian.com/ja/browse/JSP-161709

    It just needed more memory. 

  4. DIM

    Jun 06, 2013

    What's inside version 6.2.2.2? I don't find release notes...

  5. Jason Lang

    Jun 06, 2013

    Also, the download link appears to try and download plugin.jar instead of the full, normal GreenHopper plugin jar file.

  6. Remon van Gijn

    Jun 10, 2013

    Seems the upgrade issue to 6.2.2. was the direct reason to update it now to 6.2.2.2

    Indeed, also our instance required a shoot/reboot to get going again.

    https://jira.atlassian.com/browse/GHS/fixforversion/33293

     

  7. HVDeveloper

    Jun 13, 2013

    What about Ipad compatibility? IpadAware? GreenHopper 6.0 Release Notes#iPadaware

    GHS-8794 - Getting issue details... STATUS



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.