Versions
releaseDate
Finds issues by the release date of the associated version (fix versions, affects versions, version custom fields).
For example to find issues that have a fix version of any release that is due in the next 10 days:
To find issues where the fix version will be released on a given day:
You can use any of the following predicates in these version functions:
Table 2. Predicates
Name | Argument Type |
after - commented after | date or date expression, or date function, eg startOfDay(), lastLogin() |
before - commented before | date or date expression, or date function |
on - commented on this day | date or date expression, or date function |
startDate
Finds issues by the start date of the associated version (fix versions, affects versions, version custom fields).
For example to find any issues that have a fix version that is not going to start until two weeks from now:
You can use any of the predicates in Predicates.
overdue
Finds issues by whether the associated version is overdue, optionally querying further on the release date.
An overdue version is one that is a) unreleased, and b) has it’s release date in the past.
To find all issues that are supposed to be fix in an overdue version:
Find all issues with a fix version, that is at least two weeks overdue:
earliestUnreleasedVersionByReleaseDate
Returns the earliest unreleased version by release date, as distinct from the built-function earliestUnreleasedVersion, which sorts by the version ordering.
By default archived versions are not considered. If you wish to take into account archived versions, add "true"
as a second argument, e.g.:
archivedVersions
Returns versions that have been archived. To find only versions that have not been archived just negate the query: