GitLab Ecosystem, 15 Dec 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.8 Kickoff - Create:Ecosystem

Description

Display feature flag information in Jira - https://gitlab.com/gitlab-org/gitlab/-/issues/229347

Jira issues list: Filter issues by Jira Status, Assignee and Author - https://gitlab.com/gitlab-org/gitlab/-/issues/227023

Making Jira Transition IDs easier to configure - https://gitlab.com/gitlab-org/gitlab/-/issues/16119

MR statuses not syncing in GitLab for Jira Connect application - https://gitlab.com/gitlab-org/gitlab/-/issues/229174

Allow manual data sync with Jira Connect app - https://gitlab.com/gitlab-org/gitlab/-/issues/263243

A

Hi, I'm patrick dooley, I'm the senior product manager for get lab's ecosystem group, and this is our 13-8 kickoff. It's going to be a somewhat light milestone because the holidays so happy holidays. I hope you're spending time with friends and family we're going to be working on a few items though, and the theme uh will continue to be jira this milestone, as it has been for the last few. uh The first thing I wanna talk about is feature flag.

A

Information is being added to jira, so we've got a connect application that the last few milestones we've been adding data to we've previously added branch information, we've added, build information in 137 deployment, information, thirteen, seven and then thirteen eight we're going to add feature flag data, uh so that'll complete the the set of data that the connect application can accept. So we will now be sending all available data to that and that shows up in the developer panel inside jira and then we're going to be working on the jira issues list.

A

So we added this a few milestones back and it's very basic in functionality. Right now just shows you a list of issues. What we're going to do is start working on the ability to filter those issues.

A

The first piece is filtering by status once we have the ability to do that, we can start to add more filters and make it make it more interesting um by adding different ways of slicing and dicing that data, so uh against status, assignee an author and then this will also tie into the work that we're currently in the design phase on for adding the detail view of the issue list. So that's awesome. I hope that'll make that a lot more useful and then this has slipped for some time.

A

We want to kind of revisit this and try to get this wrapped up. Our front engineer has already started work on this previously, um but right now, the way that you configure transition ids, I think we have screenshot here- is by integer and so to put in your your transition id by integer, isn't very intuitive, and what we'd like to see instead is a visual way to select available transitions and, finally, there's a bug that we're working on one of our engineers has been working on this for a little bit.

A

The mr status is not syncing to the kinect application and what we've also found from this um is we've. We've got opened up a few other issues to allow manual syncing.

A

So we've got a couple of little lightweight issues that we've added to talk about fixing this, but then also expanding that ability to be able to manually sync in a couple of different places so that when you connect your namespace that data automatically gets synced, and then you can also manually sync as well to make it easier to to get all of that data in in a consumable way, instead of only looking at future data.

A

So what that means is in your connect application. If you have used the connect application in the developer panel, it shows all of the so branches branches deployments commits builds feature flags right like that thing that we're adding in thirteen eight all of that data today only shows once it's been connected moving forward. So we need to be able. We need the ability to do that retroactively as well.

A

So that's 13 8, it's going to be a lightweight milestone, but it'll still be the best release ever and I'll. See you in january, happy holidays.