"Epic Name" as non-editable field is now required... or how to downgrade the GH version

[Pilar Cantarero]

Hi,

We have detected a bug since the "Epic Name" is now a non-editable field. We never use epics in our projects, for now this has not been a problem, but in the new plugin version, this field is required and moreover it cannot be edited from settings screen. So, in our case, the field name now applies to a specific issue type (not to all) and this behavior seems random… Any way to have this field configurable in order not to apply to our issue types?

Or, as workaround, how can I downgrade the GH version to other where this field was editable?

Thanks in advance!

[Immanuel Siagian [Atlassian]]

Hi Pilar,

There is a discussion here on downgrading a GH version: https://answers.atlassian.com/questions/144634/downgrade-to-6-0-7-from-6-1-3-2

As you may notice from the thread:

Installing older GreenHopper version into the JIRA instance will not downgrade the GreenHopper related data. Thus, if you have database backup or XML backup generated before the plugin upgrade, you can roll-back using those backup data.

Hope this info has been helpful.

Cheers

[Pilar Cantarero]

Hi Immanuel,

First of all, thanks for your reply. Unfortunately, we cannot apply that workaround at the moment. The biggest problem is why Epics fields are now non-editable! It is being a quite big problem because these fields are associated to a wrong issue type, and now, when we had decided to use epics, we cannot applied epics to the corresponding issue types! This makes no sense! Any explanation?

Thank you in advance,

Pilar