Bulk editing doesn't allow changing epic/theme

[Chris Marts]

It seems like the "Change Epic/Theme" drop-down list is working as if it was the "Change Labels" drop-down list - unless I'm mis-understanding how it is supposed to work? Notice how the "Labels" instruction is duplicated underneath the drop-down list for "Change Epic/Theme" and it behaves as a label auto-complete:

[Danielle Zhu · Accepted solution]

Yes, Epic/Theme works more or less like a label, whether on bulk edit or normal edit, except that an issue key is expected as a value of the Epic/Theme field. Here is a similar recent discussion: https://answers.atlassian.com/questions/787/what-is-the-difference-between-epic-as-issue-and-epic-theme-as-a-field-in-an-issue

[Chris Marts]

Okay - so is there a way to bulk change a list of tasks into sub-tasks and associate with an actual Epic? The scenario is that, say, several tasks exist independently and I wan to retroactively go back, create an Epic and group these tasks as sub-tasks associated with the Epic.

[Danielle Zhu]

Chris, you can't bulk convert tasks to sub-tasks. There is an open request for that: https://jira.atlassian.com/browse/JRA-13245

However you can associate tasks with an Epic without converting them to subtasks. To view all issues associated with an epic in GreenHopper, just click the epic key on the cards (see http://confluence.atlassian.com/display/GH/Working+with+Epics) If you are not using GreenHopper, clicking the epic key link in JIRA will take you to the issue navigator where all issues associated with that epic will be listed.