nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cannot edit epic name in GH rapid board

Susan Hazlett

I am the Jira administrator, and I have created a project as a sandbox to test out features in GH. On the planning board mode, with epics showing - I have two epics that have the default "unlabeled" names attached. When I try to edit the name or mark these epics as done, I get an error message that says I do not have permission to edit the name.

I created another epic, and have no problems with that one. Any clues as to why I cannot edit the previously existing epic on the rapid board (planning mode)?

Permissions are set correctly, as I have demonstrated with creating a new epic. Roles are set correctly as well.

I'm at a loss as to where to look.

Thanks!

Accepted answers

Susan Hazlett

I think that this was just a bug on that one issue, as I was able to do everything to all other epic's that did not have a label name, including mark them as complete.

All comments

Susan Hazlett

I think that this was just a bug on that one issue, as I was able to do everything to all other epic's that did not have a label name, including mark them as complete.

Susan Hazlett

I ended up just deleting that test issue because everything I did with it seemed to cause an error, and I couldn't reproduce it with any other issue.

Dobroslawa Wierzbicka

To anyone who might still be interested in this or similar issues, this situation suggests some mismatch in the Epic-related Custom Fields.

names beginning with "unlabelled" (with Issue Key following) are a result of the Epic Name field being empty;
the permissions error will be displayed even if the user has relevant rights in Jira, but the Epic is Resolved or Closed - then Greenhopper won't be allowed to edit the Epic Status field.

New Epics were correctly, most likely because re-indexing took place in the meantime, and field inconsistencies were fixed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-software-cloud