GitLab Import Group, 30 Nov 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Walkthrough: Import from FogBugz into GitLab

Description

Haris Delalić from the Import Team walks through import from FogBugz into GitLab.

A

Hi everyone,: this is haris delalic and I am the product manager.

A

For group import here at gitlab. today,, I'm going to walk through an import from fogbugz into gitlab.

A

To show the current user experience and note any opportunities for improvement. fogbugz.

A

Is one of our least-used importers and is currently not getting any engineering time.

A

So I was curious to see it in action. I'll start by pointing out that the only objects.

A

That I expect to be imported from fogbugz are issues.. This is one of our issues. Importers.

A

I've created a sample project in fog bugs, and I have set up several different columns with.

A

Different cases on them bug bugs calls issues cases so to start the process.

A

I'm going to create a new project in gitlab by starting an import and selecting fog bugs.

A

Once I provide my project url as well as my credentials, I'm able to continue to the next step.

A

I also know that this is my first time importing from fogbugz, so.

A

I do not know what this will look like and what experience I'm gonna get out of this.

A

So it does seem that this is one of the few importers that we have that allows you to map.

A

Users manually.

A

So the default in this case is an empty deployed user field.

A

So, let's see the user map.

A

The default is mapping all the fogbugz account ids to full name and then an empty gitlab user.

A

Field will add the firefox user name. So if I leave this empty, it will add the full name.

A

In the description for the issues and comments.

A

And it will associate all of those issues with the project creator, so I will be the owner of the.

A

Issues and the comments and the actual thoughtbox username will be added in the description.

A

However, if I map a fogbugz account to a gitlab user, then I would expect a full.

A

Full link between the two users. So if I select.

A

A

As the mapped user here, I should get the full mapping in the end.

A

So continue to the next step.

A

It does look like and like I can go back and customize the email addresses and usernames.

A

And how that's imported? um There are two repositories that are available.

A

However, this may be a misnomer, because it is not really repositories. It is.

A

Projects so there's an onboarding project and an inbox and onboarding project is.

A

A planner, so what they call a planner is a board that then contains.

A

Buckets of items.

A

So I'm able to map a planner.

A

To a project in gitlab.

A

So I can map the onboarding project planner to an onboarding project.

A

New project being created, so I will rename this.

A

So that I can more easily find.

A

This project, in my under my name later.

A

So now that I'm happy with this name.

A

I will import the project or the planner.

A

So the weirdity that I noticed is that, even though I typed in a different name.

A

It seems like wanted to rename it back to the original. It did not take the name that I gave it.

A

However,, it does appear to have completed successfully and fairly quickly, given it.

A

Was a smaller project, so I will click on go to project, to see what I have.

B

Okay, so it did not take the name that I typed in it did default back to.

A

The original name, which was onboarding project.

A

Looking at activity, I can see that it was imported.

A

A

Bug inquiry must fix. I am not sure if these labels actually came from fog bugs.

A

Because in fog bugs on one of my issues, I have blue I've used a few labels.

A

And I am not even able to see the labels here.

A

But in this case here I have added tags which I expected sort of to be translated into labels.

A

Which doesn't seem to be the case.

A

So there's definitely priority here. There are sub cases, estimates story, points and I'll try to.

A

See where each one of these landed and how much of this was really imported, but to begin with.

A

The labels- I don't quite recognize, but this must fix label- looks a lot.

A

Like the priority here,.

A

So, who knows, if that's that's, why I have the must fix.

A

Label in gitlab.

A

So members, just myself.

A

Interesting that the person who I've added to be the.

A

Owner of the issues did not get added to the project, so looking at the issues themselves,.

A

I see that they were.

A

Tagged with bug and must fix being the priority and then bug and inquiry being more of the type.

A

Of an issue is when I create a new issue.

A

I guess I probably should have tried some of.

A

Some of the other priorities and then imported just to see if these would get added. But there's.

A

Also, a category of bug versus feature versus inquiry versus schedule items. It seems like.

A

The category was imported as a label, and then the priority was imported as another label in gitlab.

A

So, looking at this one issue that I added.

A

It does seem to have mapped the issue to the user that I specified in gitlab.

A

uh The text has come across, however, the icon, which was an image that I attached in the description.

A

Did not come across.

A

So this was mainly plain text that we were able to import.

A

And then each one of these.

A

Comments on the issue was assigned to the appropriate user, but also prefixed, with a note.

A

Stating when and where and by whom was it created.

A

And then there was no comment for this change, because this was an.

A

Automated uh pretty much an event that happened on the issue.

A

And you can tell here which event it was there's just a lot of extra information that.

A

May not be useful and seems pretty busy, so maybe these could have been events versus comments.

A

Or we should recognize that they were events and still imported as comments, but not.

A

With all this extra with all these extra notes,.

A

So I don't have the weight feature, so I can't tell if that was something that would have come across.

A

um The only thing that I see set here is.

A

Are the labels and the assignee.

A

So I see nothing else that might have come across.

A

So, looking at a few more issues, essentially like closing fog, bugs.

A

So issue number two creature: first projects does have some urls and a bolded portion.

A

So I wonder if any of that styling came across.

A

Issue number did come across, which is nice, so that.

A

The numbers do match: that's awesome. The url links were.

A

Lost in translation, and so was the bolded video tutorial.

A

Part of the text, so it seems that the markup is lost and we only got pure text out.

A

Okay, so, all in all,, I can report that it does seem to work in a very limited capacity.

A

But all issues have made it across.

A

I think that's all that I have for this test.

A

This was very helpful to me in understanding how this works and what seems to work for fogbugz.

A

Thank you for watching the video.