Static Code Ticket Data Model
The Static Code Ticket data model is a record that documents the interactions and progress made on a single or group of static code findings. It extends the Ticket data model.
The following table details the default attributes of the Static Code Ticket data model:
|Order||Attribute Name||Attribute Type||Relationship Type||Required|
|1||Reference (Static code finding)||No|
|2||Reference (Static code finding)||No|
|3||Calculated (Single Choice)||N/A||No|
|4||Calculated (Date Time)||N/A||No|
|8||Calculated (Single Choice)||N/A||No|
|11||Calculated (Date Time)||N/A||No|
|12||Calculated (Single Choice)||N/A||No|
|25||Reference (Sprint Model)||No|
|28||Risk Scoring Model||N/A||No|
|36||Source data models icons||N/A||No|
|43||Reference (Base model)||No|
- The Order column specifies the order of attributes being calculated in data computation.
- The attribute names are used in Brinqa Query Language (BQL) queries and Brinqa Condition Language (BCL) predicates.
- In the Type column, Calculated means that the value of the attribute is computed by executing a script. The text in the parentheses after Calculated denotes the type of the outcome.
- In the Type column, Reference means that two data models are related. The name in the parentheses after Reference indicates the other data model.
- The Relationship Type column only applies to the Reference type attributes. You can use the relationship type keyword in BQL queries.