Add "project" filter option to group-level dependencies app

@dpisek, Please add a group or category label to identify issue ownership.

You can refer to the Features by Group handbook page for guidance.

If you are unsure about the correct group, please do not leave the issue without a group label, and refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issue.

This message was generated automatically. You're welcome to improve it.

This issue was automatically tagged with the label groupproject management by TanukiStan, a machine learning classification model, with a probability of 0.57.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

changed the description

added automation:ml groupproject management labels

added devopsplan sectiondev labels

changed the description

marked this issue as blocked by #422353 (closed)

set weight to 5

Setting label(s) Category:Team Planning based on groupproject management.

added Category:Team Planning label

added Category:Dependency Management automation:ml wrong frontend groupthreat insights workflowready for development labels and removed Category:Team Planning groupproject management labels

@thiagocsf, thank you for moving this issue to workflowready for development.

Please add a type:: label to indicate the work type classification.

This message was generated automatically. You're welcome to improve it.

added devopsgovern sectionsec labels and removed devopsplan sectiondev labels

added featureenhancement label

added typefeature label

@dpisek - Assigning this issue to %16.4 based on Add filter UI-component to group-level dependen... (#422353 - closed). Please adjust as necessary.

@abellucci - Thanks for the ping!

I am happy to pick this up for %16.4, but it also depends on where the backend is at. The frontend is already a little bit ahead.

@mokhax and I are syncing up tomorrow, and we can discuss this

PS.: Related to this: Currently we are using one feature flag for all the changes around the group-level dependencies. That includes the filtering, which, I think, is the biggest piece of work.

But we could potentially take a more iterative and fine-grained approach and release some features earlier (displaying the licence data on the report, sort-by license name). It means a bit of extra feature-flag management, so I wanted to check with you if you think it's worth it

I have the backend work defined in #422294 (closed). I can schedule it for %16.5 or add it to %16.4 and see if we can squeeze it in. @abellucci, @dpisek WDYT?

@mokhax - Sorry for my delayed response.

@dpisek - Have you already started this work in Draft: Resolve "Add "project" filter option to ... (!132366 - closed)?

@abellucci - Yes, that is correct!

I actually picked it up as my first task this milestone, but then @mokhax and I agreed that it would be better to tackle #422355 (closed) first, as it follows the other work we've been doing around licenses.

Once the MR that addresses #422355 (closed) is merged, I can get back to adding the project filter

@abellucci, @dpisek I would like to schedule #422294 (closed) (backend) and #422356 (closed) (frontend) for %16.6. That will allow us to focus on delivering the license filtering for %16.5 and then we can focus on the project filter in %16.6. WDYT?

That sounds good to me @mokhax! I went ahead and updated the milestone and added these two issues to Threat Insights 16.6 Planning (#427942 - closed).