We use greenhopper 10.1 and its agile board functionalities. We also use to create epics to group feature related user stories.
We noticed that after an epic and respective children user stories are closed, the epic still appear in the epic pannel.
Is this the expected result? How can we hide the closed epics from the epic pannel.
Thanks in advance
The "Mark as Done" option might not show up if you don't have permission to edit the epic, or also if your epic field configuration has changed. Also, the functionality to mark as done was introduced in GreenHopper 6.1 (the latest version is 6.1.7).
Please can you check the following:
* If Epics is enabled through GreenHopper Labs, then you are on an older version of GreenHopper (go to GreenHopper Labs in Admin and look for an Epics checkbox)
* If you are unable to edit the epic name, it coud be a permissions issue (unlikely)
* Go to the Custom Fields, look for the Epic Status field and click "View", and check what appears under Options - you should have the following:
If it's none of these things then please raise a ticket at https://support.atlassian.com and they can help diagnose what's going on.
It sems that in order to have the "mark as Done" available in my Epics pannel I need to switch my configurations to GreenHopper Simplified Workflow.
I'm not able to change it rigth now since I need to contact administrator to do that.
Thanks a lot for yout hints
Joanne's answer above about setting the Epic Status is what made the 'Mark as Done' menu item show up in the Plan board for me. I have On Demand 6.2.3 and have used Epics since the 'Labs' days. When the new Epics were added to Greenhopper, there were 2 Epic Status fields showing in the Custom Fields. 1 of them had the Options set as shown above, but the second Epic Status field didn't have any Values. I simply added the Values shown in the Screenshot above and clicked Done. Now Mark as Done shows up in the plan board and works as designed.
i'm having a very similar issue now we're on the latest JIRA version - I've marked an EPIC as 'closed' on it's actual page, however when going back to the backlog and looking down the epic pane I cannot mark the epic as 'done' because if its 'workflow status'.
In the old JIRA, when an epic was marked as done, you could then go back into the backlog, look on the pane with the epics and mark as done from there, and therefore removing that epic from that pane and archiving it.
How can I again move completed epics out of the backlog epic pane?
You raised this as on demand, and for the GreenHopper on demand platform, it is always updated with the latest version, therefore I presume that you are running the latest version at the time I posted the answer.
For your case, as answered below by Joanne, to get the best out of GreenHopper, please consider upgrading to later version to get the most out of it :)
Or alternatively, you can provide the version used together with which version of Jira used so that the community can suggest the most appropriate workaround for this :)
I'm having the same issue you had in 2013 but I'm now on the latest cloud version. I have no idea why i can't "mark as done" from the board, nor why the epics will not disappear from the board once I've marked them as "done" from the details view. Can you help? Thanks!
Hello, I've just confirmed that "my" Greenhopper version does not support the Mark as Done feature.
The option “Mark as done“ in Epic panel is available only in Green Hopper 6.1 version above.
Currently Jira is using Green Hopper 6.0.8 version that is why you are not able to view this option in the Epic panel.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs