...
Type | Documentation | Field name (use it in AUX.JQL and AUX.GETFIELD) | Notes |
---|---|---|---|
ApplicationUser | Javadocs | ASSIGNEEOBJECT, CREATOROBJECT, REPORTEROBJECT | |
Project | Javadocs | PROJECTOBJECT | |
Version | Javadocs | AFFECTEDVERSIONS, FIXVERSIONS | Mentioned fields returns collection of Versions - Collection<Version> in Java. |
ProjectComponent | Javadocs | COMPONENTS | Field returns collection of Compoents - Collection<Version> in Java. |
Attachment | Javadocs | ATTACHMENTS | Field return collection - Collection<Attachment> in Java. |
Label | Javadocs | LABELS | Field return collection - Collection<Label> in Java. |
IssueType | Javadocs | ISSUETYPEOBJECT |
Collections
Having several fields of issue as Collection of java objects is the main reason that, Smart QL does not handle all issue fields on its own and convert it to SQL types. Flattening collection to a column/row value loses information, whether letting handling them by user with XPATH expressions gives more flexibility and power. See examples:
...