To filter your data in an easy and powerful way, we designed our own query language: AWS Blu Insights Query Language (BQL).
How to use it?
Just type your BQL query in the filter field displayed on top of almost every page.
Constructing BQL queries
This section describes information about fields that are used for searching. A field in BQL is a word that represents a AWS Blu Insights artifact. In a statement, a field is followed by an operator, which in turn is followed by one value or a regular expression (regex). The operator compares the value of the field with the value on the right, such that only true results are retrieved by the statement.
Types
|
Type
|
Supported operators
|
Value types
|
Examples
|
|
string
|
=, !=, like, not like |
String with single or double quotes
|
name = 'file.ext' would result in all files with names starting with disc |
in, in all, not in |
Array of strings with double or single quotes
|
workpackage in ['Workpackage1', 'Workpackage2'] would result all workpackages in Workpackage1 or Workpackage2
workpackage in all ['Workpackage1', 'Workpackage2']would result all workpackages in Workpackage1 and Workpackage2 at the same time |
|
|
number
|
=, !=, <, >, <=, >=, between ... and ... |
numbers
|
effective lines > 5 |
|
date
|
=, !=, <, >, <=, >=, between ... and ... |
date formatted like YYYY-MM-DD or YYYY/MM/DD
|
start date > 2021/02/10 |
An additional operator is Empty is available for every types. This operator works without value type, e.g. name is empty.
Fields
|
Field
|
Description
|
Type
|
Applied to
|
|
name
|
|
string
|
Assets
To-Dos
Management
|
|
title
|
|
string
|
To-Dos
|
| description |
|
string
|
To-Dos
|
|
file type
|
|
string
|
Assets
Management
|
|
assigned to
|
|
string
|
Assets
To-Dos
Management
|
|
status
|
|
string
|
Assets
To-Dos
Management
|
|
path
|
|
string
|
Assets
Management
|
|
effective lines
|
|
number
|
Assets
Management
|
|
comment lines
|
|
number
|
Assets
Management
|
|
empty lines
|
|
number
|
Assets
Management
|
|
start date
|
|
date
|
Assets
To-Dos
Management
|
|
end date
|
|
date
|
Assets
To-Dos
Management
|
|
workpackage
|
|
string
|
Assets
To-Dos
Management
|
|
issue
|
|
string
|
Assets
Management
|
|
label
|
|
string
|
Assets
To-Dos
Management
|
|
board
|
|
string
|
To-Dos
Management
|
|
number of workpackages
|
|
number
|
Assets
To-Dos
Management
|
|
number of labels
|
|
number
|
Assets
To-Dos
Management
|
|
number of issues
|
|
number
|
Management > Test Scenarios
|
|
number of CI/CD jobs
|
|
number
|
Management > Test Scenarios
|
|
number of comments
|
|
number
|
Assets
Management
|
|
cyclomatic complexity
|
|
number
|
Assets
Management
|
|
indegree
|
Number of ingoing edges (parents)
|
number
|
Assets > Dependencies
|
|
outdegree
|
Number of outgoing edges (children)
|
number
|
Assets > Dependencies
|
|
node type
|
|
string
|
Assets > Dependencies
|
|
link type
|
|
string
|
Assets > Dependencies
|
|
homonym types
|
has the value ‘identical’ if the file has identical homonyms
|
string
|
Assets > Homonyms
|
|
project name
|
|
string
|
Pipeline
|
|
support method
|
|
string
|
Pipeline
|
|
target cloud
|
|
string
|
Pipeline
|
|
target database
|
|
string
|
Pipeline
|
|
target technology
|
|
string
|
Pipeline
|
|
product type
|
|
string
|
Pipeline
|
|
project size
|
|
string
|
Pipeline
|
|
legacy technology
|
|
string
|
Pipeline
|
|
customer name
|
|
string
|
Pipeline
|
|
business domain
|
|
string
|
Pipeline
|
|
additional technology
|
|
string
|
Pipeline
|
|
world region
|
|
string
|
Pipeline
|
|
unicode option
|
|
string
|
Pipeline
|
|
nb batches
|
number of batches
|
number
|
Pipeline
|
|
nb reports
|
number of reports
|
number
|
Pipeline
|
|
nb screens
|
number of screens
|
number
|
Pipeline
|
|
nb transactions
|
number of transactions
|
number
|
Pipeline
|
|
stored procedures
|
|
number
|
Pipeline
|
|
total line of code
|
|
number
|
Pipeline
|
|
total tests
|
|
number
|
Pipeline
|
|
batches percent
|
|
number
|
Pipeline
|
|
screens percent
|
|
number
|
Pipeline
|
|
transactions percent
|
|
number
|
Pipeline
|
|
database files
|
|
number
|
Pipeline
|
|
database queues
|
|
number
|
Pipeline
|
|
database size
|
|
number
|
Pipeline
|
|
database triggers
|
|
number
|
Pipeline
|
|
database views
|
|
number
|
Pipeline
|
|
total budget
|
|
number
|
Pipeline
|
|
total duration (in month)
|
|
number
|
Pipeline
|
|
poc/pilot total line of code
|
|
number
|
Pipeline
|
|
partners
|
|
string
|
Pipeline
|
|
legacy database
|
|
string
|
Pipeline
|
|
number of partners
|
|
number
|
Pipeline
|
|
number of legacy database
|
|
number
|
Pipeline
|
|
created at
|
|
date
|
Pipeline
|
|
go live
|
|
date
|
Pipeline
|
|
kick off
|
|
date
|
Pipeline
|
Note
The “=” operator can be used with ‘uncategorized‘ like workpackage = ‘uncategorized’. This operation is similar to workpackage is empty. The fields available are Workpackage, Status and Label.
Logical operators
To build even more complex filters, you can use logical operators “and” and “or”. You can also use parentheses to group your conditions. Thus, you can build powerful filters such as:
(name like '\\.CBL' and workpackage in ['WP1', 'WP2']) or start date between 2021/04/10 and 2021/04/25
Running a saved search
Saved searches are shown on the left side of the advanced search input. Click on the “filter” button on the left side of the search input to display it.
To run a filter, e.g. Epics, simply click it. The BQL for the search will be set, and the search results will be displayed.