Migration fails when Jira Reporter is "Anonymous" about jira2gitlab HOT 4 CLOSED

A little good neews, sort of :-)

The only way I have worked around this for now is simply... DELETING the offending issues (in jira) and then starting over. Thus far I only ran into a small handful of offending (anonymous) issues in a large project (2300 issues); and the "offending" issues were to be honest, ones we really didn't care about and held no historical significance.

But as we move on to migrating the remainder of jira projects, this has a bit of potential to be a problem. I assume internal the "anonyous" reporter in Jira is actually a blank or NULL or some such similar deal. In jira it shows up as "Anonymous" in ITALICS. Not sure what you would do to set the reporter to but guess it could be a customizable field, or just set to the root user or.. ??

from jira2gitlab.

The error suggests that the reporter field is completely missing. The commit above should fix this. The Gitlab issue will be created as reported by the admin user.

from jira2gitlab.

Fantastic! Thank you so veery much.

I'm hoping all this commit activity ends up pushing your code to the top of the search list when someone else is looking to export jira to gitlab. Most certinly the best of the bunch.

from jira2gitlab.

I also agree that the (reporter) field is most very likely empty in these cases. Very odd, one of the issues I found that had this state was reported by a user that still existed in our jira users-list. But no way to search for "Anonymous" or "" reporter to try to bulk-fix it in jira. I assume for one weird reason or another that across the years the handful of issues this happend to broke somehow during one of the million upgrades I did over the years or......

from jira2gitlab.