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

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).
If you are using the new boards, please see Creating an Epic

 

エピックは多くの作業量を必要とします。エピックは基本的に大きなユーザーストーリーで、いくつかの小さなストーリーに分割できます。1 つのエピックを完了するのに、数個のスプリントが必要になる場合があります。 

エピックは、ストーリーを管理する追加の階層として機能し、プロジェクト内またはプロジェクトをまたぐ課題グループに対して、計画立案する際の指針としての役割を果たします。エピックを活用することによって、スクラムマスターとプロダクトマネージャーは、すべて共通のテーマで関連している重要な課題グループを測定することができます。

エピックを作成するおよびエピックに課題を追加するを参照してください。

(Note: In JIRA, epic is a searchable field — see the JIRA JQL documentation for details.)

エピックの詳細については、次の 2 つの優れた記事が提供されています。

Epics are implemented in GreenHopper via a JIRA custom field of type 'label', which is used to associate cards with a parent epic.

From GreenHopper 5.3, your GreenHopper project must use the 'Scrum' template to successfully work with Epics. Upon applying this template to your GreenHopper project, you will then be able to associate Epics with other GreenHopper issue types and vice versa (as described in Working with Epics in GreenHopper Classic).

16 Comments

  1. Anonymous

    Jan 31, 2011

    From Jira 4.2 Labels are included by default so do not need the Labels Plugin.

  2. Anonymous

    May 17, 2011

    Is it really necessary to use the Scrum-Template? We are using the default-Template and it would be a great effort to change the whole think, but we would like to use the epic-feature.

  3. Anonymous

    Aug 24, 2011

    How do I set up a custom Epic field for an existing project that is not using the Scrum template?

  4. Anonymous

    Sept 30, 2011

    I question the statement "From GreenHopper 5.3, your GreenHopper project must use the 'Scrum' template to successfully work with Epics." I have set up epics without the template and the only thing missing is that the the epic field is automatically set to the  issue ID when an epic is created.

    Could this statement be clarified? What exactly is not supposed to work?

    I'd also like to know how the setting of the epic field is done automatically. Can this be enabled without the template.

     

    1. Olivier Bourquin

      Dec 05, 2011

      I'm also very interested to know how this can be achieved without the scrum template. If it's not possible, then why provide a way to create other templates?

      1. Nicholas Muldoon [Atlassian]

        Dec 06, 2011

        Hi Olivier,

        With the Scrum template we know which issue types will be available due to the use of the GreenHopper Scrum Issue Type Scheme. One of the difficulties we have encountered occurs when a customer changes the issue type scheme without GreenHopper's knowledge.

        As this can cause problems we stick to the Scrum template when we provide the Epics functionality so that GreenHopper knows there should be an "Epic" issue type to link a "Story", "Task", etc to.

        Thanks Olivier,

        Nicholas Muldoon

        1. Olivier Bourquin

          Dec 06, 2011

          Hi Nicholas,

          Thanks for you answer.

          However, is it possible to get the same feature if we change the issue type scheme? We are a big company, have 7000+ users, 300 projects, and we definitively can't use the same issue type scheme for everybody...

          I've made different setups with different project templates, and with that, nothing works as expected...

          Thanks

          1. Nicholas Muldoon [Atlassian]

            Dec 08, 2011

            Hi Olivier,

            GHS-2468 is the issue to watch. We have plans to address a number of deficiencies with the Epic functionality in 2012.

            Thanks Olivier.

            Regards,
            Nicholas 

  5. Kim Dinh

    Jan 20, 2012

    I'm still having an issue trying to get Epics and User Stories to work and hope someone can help me.  In Rally, I can create an epic and associate user stories to the epic.  So when I open up an epic, I can see all associated stories in one swoop.  Trying to do the same thing with JIRA and just can't seem to get it to work.  I can create an Epic.  I can create stories.  I can't tie the stories to an epic. 

    We changed our template to the Scrum template and the epic field still doesn't exist in the Cards view and according to GHS-2468:
    Switch to scrum template and after that customize the view based on your need via _Agie>Tools>Configuration>Card. 
    How do I get to  _Agie>Tools>Configuration>Card???

    Thanks in advance!

    1. Anonymous

      Apr 17, 2012

      I have the same problem - I've switched to the scrum template but the epic/theme field does not show up on the card. Any ideas?

    2. Karie Kelly

      Apr 25, 2012

      To change your card styles, after navigating to your project, click on the Agile submenu. There should be a Tools option on the far left; under that menu, you select Configuration. Once you do that, you should have three tabs: General, Card Styles, and Task Mapping.  Card Styles allows you to change the colors and fields visible by issue type; task mapping allows you to define your swim lanes.

      Within Jira,we create Epics using the issue type of Epic, create our stories, and then use the Link functionality to link stories to epics. That way, when viewing the epic in Jira, I can see all associated user stories.

      Unfortunately, the Epic issue type does not work (or doesn't seem to work) with the Epic field in Greenhopper since Jira has it as an Issue Type and Greenhopper has it as a label. Labels are prone to mistypes and if we use, we cannot easily see all issues associated with that epic in a single view in Jira without creating a separate filter.  Consequently, if we use the links, we can see on the Epic all linked items and in the navigator, adding Links as a column, we can see all links too.

      We have only found value in using greenhopper for the planning and task board features to easily drag and drop JIRA items.  But, the gadgets to include on Jira and Confluence dashboards all deal with time instead of story points and use Fixed Versions instead of sprints...so, we have to create our own reports and rely on those fields.  Once there are more gadgets that can be included on these other dashboards that are the home pages for all users, then we will be happy to use more of the Greenhopper functionality.

       

  6. Anonymous

    Aug 08, 2012

    An Epic should span, cross-sectionally, multiple team story sets, and ultimately define the underpinnings finalized in consumation of a maximum duration iteration, but NEVER should an Epic cause redefinitions of subordinate story duration — otherwise the risk quotient would rise to exceed the level of the underlying intended benefits manifest.

  7. Anonymous

    Aug 08, 2012

    putniI don' t understand what you are saying. Are you saying that an epic (and subs) should span team story collections that don't entirely define the final iteration duration except as an offest of unexpected variances? This is crazy, as redefinitions of subordinate story durations can by definition never rise to exceed the level of the decided upon team manifest, unless that manny is itself determinate, and that can't ever be the case with agile. You must be a waterfall enthusiast. Welcome to the new world order. We have no bosses. We are your boss.

     

  8. Anonymous

    Dec 12, 2012

    A effective way to handle Epics and Stories is by using a Story Map. There is a StoryMap Plugin at Atlassian Marketplace: bauer-information-technology.com
    It is worth a look..

  9. Anonymous

    Feb 05, 2013

    When I create an epic I get the message "Your epic has been created but is not currently visible."

    It doesn't appear on the planning board, despite refreshing logging in/out etc.

    It feels like a config issue, but I'm pretty stumped, anyone else had this issue?


  10. Anonymous

    Feb 05, 2013

    It means one of the following: 

    • You have a quick filter turned on and the issues doesn't meet the quick filter's criteria
    • You have an epic filter turned on the issue isn't associated with the selected epic()
    • The board's filter's criteria doesn't include the issue you created. Navigate to the filter > confirm the epic doesn't appear there > then update the criteria until the epic appears and save the filter. 



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.