Epic - mark as done

[srinivasp]

I am testing the Epic issue type in JIRA 5.2.5. I created couple of sprints and completed them. Now i want to mark as complete. When i click the drop down, the list does not contain "Mark as done" option which was mentioned in the documentation. Did i miss any configuration for that?

[Rahul Savaikar]

Hello Srinivas,

Unknowing of the fact that it could create such a small issue, I had earlier created a project specific context in the "Epic Status" field configuration.

(My earlier statement was incorrect as I used "configuration" word instead of "context" - sorry about that)

I deleted this project specific context so that the "Epic Status" field configuration was Global again and hence applicable to all the projects those are GreenHopper enabled.

This helped me to retain the "Mark as Done" option.

Regards,

Rahul Savaikar

[John Garcia]

Another way to get the Epic Status marked as done is to use Workflow Transitions and Post Functions: HowTo Track Epic Status on the Control Chart. This way, you just transition them like normal issues and they mark themselves done.

[Rahul Savaikar]

Hello Srinivas,

Thank you for the inputs! However, I did not delete the Epic Status field. I only had to remove the project specific configuration and make it Global again. This did the trick for me. :)

Regards,

Rahul Savaikar

[Srinivas Patruni]

Could you please shower some info about your words "I only had to remove the project specific configuration and make it Global again."

[John Garcia]

I think he means the project specific field configuration for the Epic Status field, if I were to guess

[Rahul Savaikar]

Hello,

I am facing a similar problem too.

- Only one "Epic Name" GreenHopper field available correctly

- "Epic Status" GreenHopper field is available in View and Edit screens with the 3 Default options (*To Do, In Progress and Done)

- Re-Indexing done

- Edit permissions set correctly

- GreenHopper Project Template set to use "Scrum" by default

I am still unable to see the "Mark as Done" option under the drop-down that appears.

Jira version: 5.2 Build #812

GreenHopper Version: 6.1.3.2

Reference:
- https://answers.atlassian.com/questions/114059/no-option-to-mark-as-done-for-an-epic-in-greenhopper-6-1

- https://confluence.atlassian.com/display/AGILE/Completing+an+Epic

- https://confluence.atlassian.com/pages/viewpage.action?pageId=321848105

- https://answers.atlassian.com/questions/145839/epic-mark-as-done

Please suggest.

Regards,

Rahul Savaikar

[srinivasp]

Delete the custom field Epic Status and create an Epic issue. You would get the Mark as Done option. If the custom field is locked follow the link to unlock and delete. Make sure you shutdown JIRA while doing DB updates.

https://confluence.atlassian.com/display/GHKB/How+to+unlock+a+Locked+field

[Teck-En]

Srivinas, you may want to check out this KB article: https://confluence.atlassian.com/pages/viewpage.action?pageId=321848105

Check if the options are missing in the custom field Epic Status. Otherwise, you have to add the options manually.

Eg.

[srinivasp]

Strange.. I found two sections. What should i do now?

ns. what should i do now?

[Teck-En]

What do you mean by 2 section? Did you meant that you had 2 Epic Status field in the custom field page?

If that's the case, I'm afraid that you had hit into a known issue in Greenhopper which is duplicate field in Greenhopper especially upgrade. You may refer to this KB article and get help from Atlassian on this matter: https://confluence.atlassian.com/display/GHKB/How+to+Fix+the+Duplicate+GreenHopper+Custom+Fields+After+Upgrading

If you don't have duplicate Epic Status field, do feel free to explain more on the 2 sections so we can understand the problem better. :)

[srinivasp]

There is only one epic status field in the custom field page. When i try to configure the Epic status custom field, there are two different configuration sections found.

[dleng]

Can you double-check if you have the "Edit Issue" permission in the project that is holding the epic?

[srinivasp]

I am JIRA admin.. so I should have that permission.