Skip to content

No labels!

There aren’t any labels for this repository quite yet.

29 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
architecture improvement
architecture improvement
Architecture refactor or improvement is needed
5
bug
bug
use for describing something not working as expected
37
community support
community support
use to identify an issue related to feature developed & maintained by community.
26
community
community
use to identify PR from community
11
critical
critical
use to identify critical bug to fix ASAP
dependencies
dependencies
use for pull requests that update a dependency file
4
do not merge
do not merge
Do not merge this PR until this tag will be removed
3
duplicate
duplicate
use to identify issue already existing
enterprise edition
enterprise edition
use to identify feature part of the Enterprise Edition licence
epic
epic
use to identify issue that will be heavily chunked
feature
feature
use for describing a new feature to develop
207
filigran support
filigran support
[optional] use to identify an issue related to feature developed & maintained by Filigran.
10
filigran team
filigran team
use to identify PR from the Filigran team
15
fix cloud ready
fix cloud ready
Fix for cloud ready
3
inactivity
inactivity
multi-repository
multi-repository
When a PR requires several repository changes
needs more info
needs more info
Intel needed about the use case
7
needs triage
needs triage
use to identify issue needing triage from Filigran Product team
70
partner support
partner support
use to identify an issue related to feature developed & maintained by the third-party vendor.
5
partner
partner
used to identify PR from patner
question
question
use for asking information about a functionality or behavior
53
regression
regression
security
security
use to identify issue related to security
solved
solved
use to identify issue that has been solved (must be linked to the solving PR)
technical improvement
technical improvement
Technical refactor or improvement is needed
4
test automation
test automation
use to identify issue related to test automation implementation
1
tiny
tiny
use to identify tiny feature to develop or bug to fix (< a week to solve)
to be deprecated
to be deprecated
Use to identify feature/part to be deprecated and to follow
wontfix
wontfix
use to identify issue that won’t be worked on