GitLab GitLab Group Kickoffs - Create:Ecosystem, 16 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab Ecosystem 13.7 Kickoff

Description

This month's upcoming highlights are:

Integrations should have a way to be reset/unlinked from inheriting projects - https://gitlab.com/gitlab-org/gitlab/-/issues/273778

Document Usage of Jira Connect application with Self-hosted GitLab - https://gitlab.com/gitlab-org/gitlab/-/issues/268278

Display Build information in Jira Connect App - https://gitlab.com/gitlab-org/gitlab/-/issues/14178

Display Deployment information within Jira - https://gitlab.com/gitlab-org/gitlab/-/issues/27986

Support individual user credentials for Jira integration - https://gitlab.com/gitlab-org/gitlab/-/issues/283923

Add Issue Detail view from Jira Issue List (Design only, this milestone) - https://gitlab.com/gitlab-org/gitlab/-/issues/220999

---

And, in case you missed it, the video talking about our new Group Integration Management: https://www.youtube.com/watch?v=6mz1y15JEHE

A

Hello there I'm patrick dooley, I'm the senior product manager for gitlab's ecosystem group and we're here to talk about our 13.7 plan. Let's get into a couple issues that we're going to work on so in 1306 136, which should have just been going out when you're viewing this or it's about to go out when you're viewing this.

A

We just launched a new awesome feature that I can link to the youtube video about. We added the ability to manage integrations at a group level which is really exciting. Here's one of the problems that we've run into because we added this and started playing with it more. We realized that there's no way to remove an inherited integration uh or an integration at all.

A

What ends up happening is you can clear out that value and kind of hit save and turn it set it to be inactive, but, as this little demo here shows like you, can't actually get rid of the values in there. That's an issue, so we need to solve that. We've got a couple of issues in here, open that we'll be working on beyond our work on group integration. That's been going on for a while.

A

We've also been working a lot on the jira connect application, so this is a an application in the jira marketplace or the atlassian marketplace that allows you to add gitlab functionality into your jira cloud installation.

A

We've got two pieces of data we'd like to add, and we also want to better document how the connect app works with self-hosted gitlab. There are some workarounds in here and if you read this issue, it kind of illustrates what can be done, but it's designed to out-of-the-box work with gitlab.com and jira cloud.

A

If you want to use self-hosted gitlab, there are a couple of workarounds available. Additionally, we want to add build information and deployment information to that connect, app, so we'll ship that information as well. So when you cut a new deployment that deployment can show inside of the jira development panel, we're also looking at expanding the jira issue list feature that we released a few milestones back. So if you remember it adds the ability for you to see a list of jira issues inside of your gitlab ui, that's really cool.

A

We have a lot of developers who give us feedback around how they love gitlab and they have to use jira, but they don't really want to leave gitlab their organization, their team, whatever has chosen jira for project tracking or work tracking and project management, but they want to be able to use git lab in their normal day-to-day process.

A

So we added the the jira issue list feature so that you can see a list of the work tasks that have been assigned to you and and get data about that. So you can do your job in get lab, but without the ability to use your individual user credentials, you can't view the details of an issue or comment on the issue or change the status of an issue. Those pieces are critical, so this issue that you're looking at today is supporting individual user credentials for that integration.

A

Our access group did an awesome job, adding that in 13 4 now we need to leverage those credentials and then once we have those we also have. This is a design issue in 13, 7 and 13 8 we're hoping to be able to execute. Now we actually want to be able to view those issue details, so you can today see a list of issues.

A

What we're hoping is tomorrow, you can see the details of those issues and then, after that you can comment edit, modify change, the status of et cetera and what we're hoping is at that point, you can spend 90 of your time inside gitlab, even if your team is using jira, that's it for 13.7.

A

We also have a couple of new members joining our team. That's super exciting, so we're still getting them ramped up. We don't see our velocity changing dramatically overnight, but we are super excited to have them on board and we're looking forward to getting them a lay of the land. So they can start helping out with some of these really exciting pieces that we're working on thanks a lot for joining me. You have a great day.