Project Labels

Project Labels

We have added the concept of project labels to FOSSA giving our users a powerful organization tool based upon the business context of each applicable project.

In this article, you learn about filtering and sorting options. As well as, bulk actions you can take to organize projects into teams or release groups

Sort Options

Title

Selecting Title within the Project(s) UI header will sort in ascending or descending

Issues

By default each project displays the total issue count across every available issue type. Issue types:

  • Licensing
  • Security
  • Quality

You may change the Issue sort by selecting Total Issues in the header and choosing your desired issue type

362

Change sort by selecting issue header

📘

Tip

  1. Selecting the header of the same issue type will change the sort from descending to ascending
  2. Issue type selection will persist throughout the user's session

Sort Type

Description

Total Issues

Display and sort total issue count across every issue type (Licensing, Security, Quality)

Licensing Issues

Display and sort by licensing issues only

Security Issues

Display and sort by security issues only

Quality Issues

Display and sort by quality issues only

Last policy scan

The default sort for the Project(s) page is Last policy scan in descending (newest --> oldest) . You may change the sort direction by selecting the Last policy scan header.

Filter Options

You now have the ability to use filters to focus your risk evaluation efforts. Please review the list below for a detailed review of each filter.

Filter Groups

Project attributes

266

Filter type

Description

CLI upload

Filter to project(s) analyzed via fossa analyze from the CLI or associated Github action

Container

Filter to project(s) analyzed via fossa container analyze from the CLI

Archive upload

Filter to project(s) analyzed via Archive Upload from one of the supported archive formats (apk, .bz2, .bzip2, .conda, .gem, .gz, .ipa, .jar, .nupkg, .rpm, .tar, .whl, .xz, .zip)

Quick Import

Filter to project(s) analyzed via Quick Import from your version control system

SBOM Import

Filter to project(s) analyzed via SBOM Import from one of the supported SBOM import formats (cycloneDX)

Visibility

273

Filter Type

Description

Public

Filter to project(s) that has a publicly accessible view without authenticating & authorizing as a FOSSA user

Private

Filter to project(s) that is not publicly accessible and requires authenticating & authorizing as a FOSSA user

Labels

313

Filter Type

Desscription

Project Label

Filter to project(s) that use a FOSSA provided or user defined project label for additional business context. Multiple labels may be selected using OR based logic.

Example: Critical Impact OR Prod

Last policy scan

269
🚧

Note

"Last policy scan" replaces "Last Updated". Last updated only represented a new project revision submitted for analysis. "Last policy scan" represents both a new project revision or a new policy scan.

For FOSSA Security users a new policy scan across all projects, will always occur after each new FOSSA vulnerability database update to ensure we've detected any new CVE's.

Filter Type

Description

Anytime

Filter to project(s) with a last policy scan at anytime

Last 7 days

Filter to project(s) with a last policy scan within the last 7 days

Last 30 days

Filter to project(s) with a last policy scan within the last 30 days

Last 120 days

Filter to project(s) with a last policy scan within the last 120 days

📘

NOTE

You can select Reset all filters to remove existing filters at any time to display all identified issues.

246

Reset all filters

Actions

In this section we will all available actions such as adding to deleting projects, adding to teams or creating release groups.

322

Bulk Actions

You can action more than one project at a time by using the select all or checking the boxes of the applicable project in the UI.

1301
❗️

IMPORTANT

By selecting the bulk action checkbox, it automatically selects all projects listed on the page. To select all applicable projects, you must click the Select all link that displays in green.

Add to team

After selecting your desired projects, you may select add to team and your desired team to add all selected projects to that team. Selecting manage teams will navigate you to the teams settings page to create, edit, or delete teams.

386

Create Release group

After selecting your desired projects, you may select create a release group to add the selected projects to a new release group. Please see Managing Projects in FOSSA] for more details on managing and creating releases.

Delete projects

After selecting your desired projects, you may select Delete from the action menu to being your permanent deletion including any issue resolutions, OAuth tokens, notifications settings, and webhooks. Select Delete from the confirmation modal to submit your deletion.

595

Release Groups

Release groups exist within their own sub navigation in the Projects UI. Please see the table below for a detailed breakdown of the differences in available functionality for projects and release groups.

1625

Feature Type

Feature Details

Projects

Release groups

Sort

Title ASC or DESC

Yes

Yes

Sort

Total Issues ASC or DESC

Yes

Yes

Sort

Licensing Issues ASC or DESC

Yes

No

Sort

Security Issues ASC or DESC

Yes

No

Sort

Quality Issues ASC or DESC

Yes

No

Sort

Last policy scan ASC or DESC

Yes

Yes

Filter

Project attributes

Yes

No

Filter

Visbility

Yes

No

Filter

Labels

Yes

No

Filter

Last policy scan

Yes

Yes

Action

Add to team

Yes

No

Action

Create release group

Yes

No

Action

Delete

Yes

Yes