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

(info) 注意:

  • 本ページは スクラムボードにのみ適用されます。

  • You will need to have the 'Edit Issue' permission in the project(s) to which the issue belongs and to which the Epic belongs. 

エピックで新しい課題を作成する

... in Plan mode

  1. JIRAにログインします。
  2. 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。

  3. ボードが表示されます。計画をクリックします。
  4. 画面左にエピックパネルが表示されない場合は、ツール > エピック パネルの表示を選択します。
  5. In the Epics panel, hover over the epic then click the triangle at the left of the epic name to display the epic details.
  6. Click Create issue in epic at the bottom of the epic details in the Epics panel.

JIRA でエピックを表示している場合

  1. 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
  2. 課題キーをクリック(または t を入力)して、課題詳細ビューを表示します。
  3. 課題詳細ビューで、課題キーをクリックするか、「 o 」を入力して、 JIRA でエピックを表示します。
  4. エピックの課題見出しの最後にある " + " クリックして ください。(スクリーンショット 1 参照)。

スクリーンショット 1 : JIRA でのエピック表示

エピックに既存の課題を追加する

... in Plan mode

  1. JIRAにログインします。
  2. 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
  3. ボードが表示されます。計画をクリックします。
  4. 画面左にエピックパネルが表示されない場合は、ツール > エピック パネルの表示を選択します。
  5. 該当のエピックの上に課題(複数可)をドラッグします。エピックが緑色に変わります。(スクリーンショット 2 参照)。
  6. エピック名は、課題の上にカラーの菱形で表示されます。

Screenshot 2: adding an issue to an epic in Plan mode

 

JIRA で課題またはストーリーを表示している場合

  1. 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
  2. 課題キーをクリック(または t を入力)して、課題詳細ビューを表示します。
  3. 課題詳細ビューで、課題キーをクリックするか、「 o 」を入力して、 JIRA でエピックを表示します。
  4. 課題を編集し、エピックリンクフィールドで該当するエピックを選択します。

50 Comments

  1. Svavar Melberg

    Can issues not be added to an epic if the sprint is already started?

    1. Not at this time. You may like to comment/watch/vote on GHS-6212 - Getting issue details... STATUS

  2. Dave Tollefson

    I tried the jql and it doesn't recognize "epic link" - gives the message "Error in the JQL Query: Expecting operator but got 'link'. The valid operators are '=', '!=', '<', '>', '<=', '>=', '~', '!~', 'IN', 'NOT IN', 'IS' and 'IS NOT'. (line 1, character 6)"

    I also tried "epiclink" but that gives "Field 'epiclink' does not exist or you do not have permission to view it."

    I looked in the advanced searching help but there's no info about epic support in jql.

     

  3. Apologies, "epic link" needs to be surrounded by quotation marks – I have amended.

    1. Dave Tollefson

      That worked.  Then I wanted to add a column to the filter results, and I found 4 new ones:  Epic Colour, Epic Label, Epic Link, and Epic Status.  I tried them all, but it would only show Epic Link in the navigator results.  Could you define somewhere what those fields are, what they apply to, and how they are used?

      1. They are documented here – I will add some more detail: GreenHopper JIRA Configuration

  4. Anonymous

    Just a couple of thoughts.  Please direct me to open issues so I may vote as needed.

     

    1. Once a story has been added to an epic, how can I remove it from an epic other than dragging it to a new epic?
    2. If I view the Epic in JIRA I would expect some kind of list of associated user stories.  Much like you can see a list of linked issues or sub-tasks on the issue.
    3. Is there a simple way to see all issues associated with an Epic besides using JQL??
    4. Is there any purpose to assigning an Epic to a user? The related stories should likely be assigned individually, so I'm not sure there's any value with assigning an Epic. Just curious about whether there's an intended use there.
    5. Is there a plan to add Epic to the Swimlane options?  That way the queries wouldn't have to be used and it would automatically create swimlanes per Epic.

    Thanks and all thoughts and comments welcome!

    1. Anonymous

      Disregard my 'how to remove" question.  I just noticed the related doc on the right.  

    2. 2. I can't see an issue for this – you may like to log one?
      3. Yes – you can click the epic in the left-hand column (I have updated this page to mention this – thanks)
      4. Not at this time.
      5. Please see GHS-6426 - Getting issue details... STATUS

  5. Philbert de Zwart

    It seems I am unable to drag the issues. Is there anything else I need to configure, or need to change about my user stories?

    This is what it looks like:

    As you can see, the user stories don't have the dots on the left to indicate them as draggable, and they indeed can't be dragged. When I try, it says that ranking is disabled.

     

    Update: This was fixed by creating a new board that had ranking enabled.

  6. Peter Degen-Portnoy

    We are just starting to use GH, though I've run Scrum and other Agile projects for quite a while.  Our sys admin enabled Epic in labs, re-indexed our database and did a point release upgrade from 6.0.7 (to 6.1?  6.0.8?  I don't know; does it matter?).  

    In the Planning board, I see my Epics, but none of them show the count of Issues.

    In this image, one can see the epic "Redo People Pages" and there should be 5 issue, 4 completed issues and 1 unestimated issues.  Also, when I select one of the epics, there are no issues visible in the backlog, although I expected to see the 1 unestimated issue.

    Because we are just moving to using GH, we have an existing "state of things".  To organize tickets, they were assigned to Fix Versions.  To view them in our Product Backlog, I wrote a new filter to select everything in these specific Fix Versions.  Might that have an impact on this display?

    1. Peter, can you please contact http://support.atlassian.com for assistance? Many thanks.

      1. Peter Degen-Portnoy

        Will do, thank you.

  7. Anonymous

    Anyway to accomplish the same task using REST? I can't seem to update the "epic link" via rest.

    Epic Link = customfield_10008

    Issue = MY-1

    Epic = MY-2

    curl -D- -u LOGIN(tongue)ASSWORD -X PUT --data '{"fields":{"customfield_10008":"MY-2"}}' -H "Content-Type: application/json" http://localhost/rest/api/2/issue/MY-1

    I get the 204 No Content response as expected, but it doesn't seem to update the field. Any suggestions?

    1. Anonymous

      ^^^ I'm using JIRA v5.1.6 and  GreenHopper 6.0.6 btw. The custom field also shows up when viewing http://localhost/rest/api/2/issue/MY-1/editmeta page. ^^^

      1. Anonymous

        Nevermind .. field is not editable according to the documents.

  8. Anonymous

    (This post basically duplicates my orginal post in 6.06 Release notes, but I thought it would be more valuable here)
    Please open a story for "As a user I would like the ability to associate issues to epics from the typical create, edit, close JIRA screens, and by inheritance bulk edit (non-scrum board) so that I can modify this data from more places and retroactively apply this new data to existing epic issue relations for more accurate reporting" 
    Context: The linking mechanism has changed and it was not retro-actively applied. I will need to do it manually to make the info displayed accurate and for properly reporting of the data.
    To date I've yet to find a user flow for adding an epic association to a story via a JIRA screen, only via the Scrum Board (described above).
    I enabled the 'Epic Link' field on all screens, but the best it will do is show the value of the field (after set via drag and drop from scrum board planning view) no form based edit-ability is available in view or edit modes that I've found to date (It also shows up in the Bulk Edit as a selectable by non-editable field).  Since the Scrum Board planning view restricts closed issues (maybe I can work around this with a custom filter) I've not found how to manually apply Issue -> Epic links using the drag and drop method for resolved work. 

    Thank you!  Dan

    1. Hi Dan, you may like to watch/vote/comment on GHS-6854 - Getting issue details... STATUS

  9. Anonymous

    How can I make the following 2 estimates appear on an epic shown in the agile overview "Plan":

    Time spent

    Remaining estimate

     

    I can see the number of issues attached to the epic, the completed issues and the unestimated issues and the original time estimate, which is a sum of all original estimates of the issues attached to the epic.

    Many thanks,

    Charlotte

    1. Hi Charlotte, you may like to log a request for this.

  10. Anonymous

    Is it possible to assign a story to multiple epics?

  11. Anonymous

    My board doesn't have Tools > Show Epic Panel. Could this be related to permissions? Afaik I'm an admin for this JIRA system.

    Martin

  12. Anonymous

    What is the best way to complete the epic, chapter, story, task model?

    It seems that Epics cannot have other epics as children? Is this true?

    So you could not have the following:

    EPIC1: Plant Gardens in our Neighborhood.

    EPIC2: Plant Garden at house 101.

    EPIC3: Plant Garden at house 102.

    With EPIC 2 and 3 being a child of EPIC 1.

    1. Correct, epics cannot be nested. The available levels are: epic > story (ie. issue) > task (ie. sub-task)

  13. Niko van Eeghen

    Hi, when adding a story to an epic (by dragging and dropping) it get's so called added to that epic and the label becomes visible.

    However, when I open the Epic in the viewer, there are no links to those stories visible. Why is this?

    1. The ability to view an epic's issues when viewing an issue in JIRA was added in GreenHopper 6.1.2. I will add this information to the page. Sorry for any inconvenience with this.

  14. Karie Kelly

    Couple of issues -

    Cannot associate an issue to an epic if no issue has yet been associated.  None of the epic fields appear on the screen, even if they are configured for all issues types and global context (all projects). 

    You should be able to associate an issue to an epic at any time regardless of whether it has items in a sprint to start or not.  Epics can take several sprints and you can identify new issues as you work on it.

    BTW - cannot access those GHS links referenced.  You accept the new SSO to allow access, but then, get an error that is cannot get a token.

    1. Kristian Borkman

      I agree it is a problem that you cannot associate an issue to an epic if no issues have yet been associated. Not all of our users go to the Plan view when creating Epics/Issues.

      1. Kristian Borkman

        I created a request to allow users to create the first issue in an epic from Jira, without having to go into the Agile Board. Vote for it here if you would also like to see this new functionality.   GHS-7900 - Getting issue details... STATUS

    2. You may like to log a request for this at https://jira.atlassian.com/browse/GHS (sorry to hear about the login problems you have encountered. Can you please raise an issue at https://support.atlassian.com/ja , and label it "lasso"? Or if you cannot log in to support either, please use the Contact Us form on our website: http://www.atlassian.com/company/contact )

      1. Karie Kelly

        Yep, I have as I was finally able to get into the Confluence site (couldn't previously because of the SSO error that I mentioned was thrown).  GHS-7889

  15. Edie Hovermale

    There appears to be a bug in Greenhopper. When entering a story I enter the Epic number in the Epic/Theme field but the story does not get connected to the Epic. I can drag and drop the Story in to the Epic via the Plan page afterwards to get the connection but I should not have to do that. It would be helpful if you fix this bug. It is very confusing and I have had to help many of our Greenhopper users navigate this issue. Thanks

    1. Karie Kelly

      Do you use the Epic/Theme field or the Epic Link? 
      I was told to use the latter.  Either way, I've logged a bug with GH because I cannot get these fields to display on the screen, even though they are on the screen definition and are configured globally (all issue types, all projects).  But, once we resolve that, would like to know the correct field to use.

      1. Edie Hovermale

        Thanks Karie,

        When editing a Story or Epic there is not a field named "Epic Link" by default just Epic/Theme. I tracked down the field through my Admin privileges and added it to the default screen but it is still not showing. This is all so confusing. I think it probably all stems from mashing Greenhopper into Jira... it is very messy and still like two different products that don't behave the same or well together. I will keep poking around.

        Thanks again for your help,

        Edie

        1. Karie Kelly

          Hi Edie,

          I thought Epic/Theme was an old GH field that was setup as a label vs having anything to with Epic issue types.  So, I've kept it hidden in the field configuration since I didn't want folks using it, but the actual Epic Name or Link to create the association.  When I unhid it and added it to the screen, it doesn't allow selection of any epics that we currently have in the system.  I'm quite confused as to how to use this functionality in JIRA as we always start in JIRA to create the epics and then start creating the stories to be associated to those epics. Currently, we were linking them - but, it would be so very helpful to use the Issues in Epic feature as it should be less prone to error and team members forgetting to link them.

          We just don't start using any boards until we are ready to either groom or plan sprints.

          The other thing that would be so very handy to see in JIRA for the epic issue types is the total number of story points (or hours if you use estimated hours) for the epic so that you can see the total scope as well as a the other statistics that are available only on the scrum boards.  Again, needed for other uses besides scrum boards and to provide those interested, a single point to go to for information about an epic.  They shouldn't have to navigate into a board just to see these details. 

          Thanks for your help!

        2. If you are using GreenHopper 6.1.3 or later, you may find the Epic Migration feature useful (if you are in doubt about anything, please contact http://support.atlassian.con before you begin).

          1. Karie Kelly

            We already looked at that; we checked all projects and all said there were 0 epics to migrate.  We never used them on the classic boards as we weren't aware of any functionality specific to epics on the classic boards. However, we definitely have issues to type=epic in our application.

  16. Mark Ariu

     

    We want to add closed issues of closed sprints to an epic that we have full epic reports also for the past.

  17. Mark Ariu

    GHS-7899 - Getting issue details... STATUS  add closed issues of closed sprints to an epic

  18. Colin Breame

    How can an issue be assigned to an epic when the epic is created?  Why isn't there a dropdown list (or similar) with the epic's for assignment?

    1. You may like to watch/vote/comment on GHS-6539 - Getting issue details... STATUS , or perhaps log a new issue for this request — thank you

      1. Pavel Bulanov

        voted. it's strange this couldn't be done now - so invonvenient to to several steps to assign issue to epic

  19. David Bennett

    I'm trying to have sub-tasks inherit the Epic from their parent stories.  I was able to do this with Components using a post-function on the create transition, but none of the Epic fields (Name, Status, Link, etc) seem to allow me to do this for Epic.  Is there a way to do this which I am somehow overlooking? 

    I am using OnDemand.

    1. Not at present, sorry. You may like to watch/vote/comment on GHS-8181 - Getting issue details... STATUS

  20. Aaron Carter

    Why aren't we allowed to see Subtasks of an Epic in the product backlog?  We we were able to see the subtasks in the Classic planning board but for some reason this feature doesn't work in the new Agile Scrum board.  Is there a way of getting around this so we can see the subtasks in the backlog and assing them to Sprints?

  21. Aaron Carter

    Why aren't we allowed to see Subtasks of an Epic in the product backlog?  We we were able to see the subtasks in the Classic planning board but for some reason this feature doesn't work in the new Agile Scrum board.  Is there a way of getting around this so we can see the subtasks in the backlog and assing them to Sprints?

  22. Aaron Carter

    Why aren't we allowed to see Subtasks of an Epic in the product backlog?  We we were able to see the subtasks in the Classic planning board but for some reason this feature doesn't work in the new Agile Scrum board.  Is there a way of getting around this so we can see the subtasks in the backlog and assing them to Sprints?

  23. Edie Hovermale

    It would also be very helpful in the planning process to have the user picture on the item in the PLAN view. We have Quick Filters that are really great but it would be really great to have the picture on the issues like in the WORK view. 

    Here is a use case:

    You have quick filters that show which assigned stories and stories in which the user is the 'Tester', a custom field, however it is not possible to test which stories are Assigned and which are Tester stories. A picture of the Assignee would do the trick.

  24. katie

    Hi, I have epic link added to my stories - when enter an issue, in the epic link dropdown I see the epics for my project but I also see a bunch of other epics that say 'unlabeled-ABC (ABC-44)'  ( Where ABC is not the currently selected project).

    When I go to the search search for all epics in the system, there are about 12 other projects using epics.. it's just this one project's issues that are showing up in my project... where can I start looking at what's causing this?

    Thx

     

  25. Betül Erucu

    Is it possible to assign one user story to severel Epics?