Support for Epics

[fraenki]

The README currently states that support for (real) Epics is missing:

Epics are currently translated to normal issues and loosely coupled via labels with their child issues
TODO: traslate them into Gitlab epics (only Gitlab Premium)

Ideally this feature would be configurable to support both GitLab OSS and GitLab Premium. When using GitLab OSS, it would use the current functionality and migrate Epics to normal issues. But with GitLab Premium it would use native Epics instead.

Are there any plans to add this functionality? Are there any known issues that prevent this feature from being added?

[ptbuchanan21]

I believe this would be added in the customfield section, found in the config file. But I could be wrong, I am still trying to figure out the metadata within the customfield section.

[swingbit]

For non-Premium Gitlab, epics (ans stories etc)are translated to normal issues indeed.

These configuration options should point at the right Jira fields:

# the Jira Epic custom field
JIRA_EPIC_FIELD = 'customfield_10103'

# the Jira Sprints custom field
JIRA_SPRINT_FIELD = 'customfield_10340'

# the Jira story points custom field
JIRA_STORY_POINTS_FIELD = 'customfield_10002'

For Premium Gitlab, I haven't had the time to implement that yet. One of the problems there is that epics in Gitlab only exist at the group level, not at the project level.

[glianeri]

What would also be good is to add an a label to an epic - in my case I wanted to add something like Team:DevOPS or Team:Dev etc.
This label would be attached to the JIRA project being imported, so it could be auto-generated from the JIRA project name if not available.