Added several more options. None of these should break your original use-case, but I needed these options for my use-case, and I think they may be helpful to others, as well. Also made GitLab asset URLs absolute. Since the relative paths will be broken, anyway, it seemed they may as well be absolute in case GitLab is still being used for SCM and can still serve the images.
-D DEFAULT_JIRA_PROJECT, --default_JIRA_project DEFAULT_JIRA_PROJECT
Optional default JIRA project name for all project
issues to be imported into (default: None)
-I INCLUDE_LIST [INCLUDE_LIST ...], --include_list INCLUDE_LIST [INCLUDE_LIST ...]
List of project names to include in dump. (Read as
space delimited arguments.) (default: None)
-m, --preserve_markdown
Do not convert GitLab MarkDown to JIRA Wiki markup.
(default: False)
-M PROJECT_MAP [PROJECT_MAP ...], --project_map PROJECT_MAP [PROJECT_MAP ...]
Map of GL project names to thier corresponding JIRA
project names. (Read as space delimited arguments of
the form oldprojname=newprojname.) (default: None)
-n, --add_GL_namespace_to_ID
Add the GL namespace to the external JIRA ID. This is
necessary if importing multiple GL projects into a
single JIRA project. (default: False)
-S STATUS_MAP [STATUS_MAP ...], --status_map STATUS_MAP [STATUS_MAP ...]
Map of GL project statuses to thier corresponding JIRA
statuses. (Read as space delimited arguments of the
form oldstatus=newstatus.) (default: None)
Added several more options. None of these should break your original use-case, but I needed these options for my use-case, and I think they may be helpful to others, as well. Also made GitLab asset URLs absolute. Since the relative paths will be broken, anyway, it seemed they may as well be absolute in case GitLab is still being used for SCM and can still serve the images.