Date: Fri, 29 Mar 2024 07:43:11 +0000 (UTC) Message-ID: <37032451.11343.1711698191567@catch-kbase-p> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_11342_767621895.1711698191565" ------=_Part_11342_767621895.1711698191565 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
EstimatedDuration is a reference field for requirements and scripts.
Two formats are supported:
The first allows you to provide a date in days, hours, minutes and secon= ds.
days.h= ours:minutes:seconds
1 day, 3 hours, 15 minutes can be written as follows:
Estima= tedDuration =3D "1.03:15:00"=20
The second format allows you provide a more readable date specifying opt= ional values for weeks, days, hours & minutes.
1 week, 2 days, 1 hour, 30 minutes can be written as follows:
Estima= tedDuration =3D "1 week, 2 days, 1 hour & 30 minutes"
Or in the shorthand form (familiar to JIRA/JQL users):
Estima= tedDuration =3D "1w 2d 1h 30m"
To find all runs where the the actual duration is within a range e.g.( 1= -4 days):
Estima= tedDuration >=3D "1 day" AND EstimatedDuration <=3D "4 days"
Alternatively, you can use the short hand "range" syntax:
Estima= tedDuration IN ["1 day", "4 days"]
Note: As dates can contain hours, minutes and seconds, testing for date = equality may not match as you would expect. It is suggested that you use da= te ranges for matching values where you are not sure of the exact time comp= onent.
=3D, <, >, <=3D, >=3D, IN, !=3D, NOT IN, = IS, IS NOT
Feature | Supported? |
---|---|
Aggregation | Yes (TimeSpan) |
Sortable | Yes |
Sub-selects | No |