6.6 ships in two builds with the same functionality: 6.6.0-jira10 for Jira 10.x and 6.6.0-jira11.3 for Jira 11.3.
Pick the build that matches your Jira version on the Marketplace page.
The release brings two new features - a Timer deadline taken from a date field and the Time between statuses field - and changes four things an administrator notices: recalculation by history, the limit of table reports, what users see without a license, and the warnings of a Cloud migration.
What changed for administrators
A Timer goal can take its deadline from a date field
A goal - and the default goal - of a Timer configuration can now use Due date or a Date Picker / Date Time Picker custom field as its deadline, instead of a fixed time. The timer counts the working time by the goal’s calendar up to the field value, follows changes of the value, is breached at once if the date has already passed, and treats a Date Picker value as the end of that day. An empty field means the goal does not match.
See Deadline from a date field. In the REST API the goal carries the field as dateFieldId - see REST API.
New field: Time between statuses
A new field type measures the working time from the first entry into a set of start statuses to the first entry into a set of end statuses, as a number in the unit you choose. It is empty until an end status is reached, is searched like a number ("Lead time" > 5) and is exported as a number.
See Time between statuses field.
Recalculation by history runs in the background
Recalculate and Recalculate Errors on the Restore by History page now run as a background job: a progress bar with counts and the time left, a Cancel button, a summary with the first errors at the end. One job runs per instance at a time. The values are set without re-indexing each issue - run one full re-index when the job has finished, so that search and JQL see them. The backfill in a field’s settings runs in the background too.
See Running in the background; the REST API takes background: true and has endpoints to follow and cancel the job - REST API.
Table reports have their own issue limit
Performance Config has a new setting, Report issue limit: the maximum number of issues a table report may select - 10 000 by default, from 1 to 100 000. The Count limit of the JQL functions (default 1000) no longer applies to table reports. A report that selects more issues finishes with an error that names the new setting; Ignore count limit exempts users and groups from it too.
On upgrade of the Jira 11.3 build, a Count limit above 10 000 is carried over into Report issue limit. On the Jira 10.x build, check the value after the upgrade.
See Report issue limit.
Without a license the issue says so
Without a valid license the Time in Status field no longer disappears from the issue: it shows a message instead of the value, and the Timer, Stopwatch and Time in Status panels show the same message instead of the values and buttons. Administrators are told to check the license in Manage apps; other users are told to contact their Jira administrator.
See The license message instead of a value.
Cloud migration names what it does not transfer
The JCMA export writes a warning for each group of settings it cannot carry to Cloud, with the count and the names. Fields that are on no screen are listed in atlassian-jira.log at startup and in the export warnings - JCMA does not migrate them. Timer goals with a deadline field and Time between statuses fields are not transferred. The Show as panel flag of Timer and Stopwatch and the order of statuses of Time in Status configurations now travel to Cloud.
See What the export warns about.
Timer/Stopwatch display cache
Performance Config has a new flag, Timer/Stopwatch display cache (5 s). It is off by default. See Performance settings - JQL.
Upgrade checklist
- Take the build for your Jira line (Jira 10.x or Jira 11.3).
- Open Performance Config and check Report issue limit against the size of your table reports.
- After a recalculation by history, run one full re-index (System → Indexing).
- If a Cloud migration is on your roadmap, read the export warnings and put the app’s fields that are on no screen onto a screen of a migrated project - see What JCMA transfers to Cloud.

