The start time of a weekly timing defaults to the current timestamp, but the default day is always Sunday. This is potentially confusing when setting up a weekly timing, and it would be more consistent if the day of the week also defaulted to today.

The once off timing is set using local time like other timings, but the calculation of its next run seems to be impacted by UTC. For 3.8.2 of the regression test doc I attempted to create a once off that runs a minute from the current time, but the home page shows the timing is due to run 10 hours from now. When the time has passed, the schedule UI still says that it is due to run once.

Attempts to add multiple exclusion periods to the daily exclusion only adds one of them. Multiple dates exclusions can be added successfully.

Deleting an Adapter clears the Partition table, which subsequently deletes all entities with cascading deletes.

When editing an adapter in IE8, the base connector dropdown becomes essentially unusable. The control has a scroll bar and makes it difficult to enter a value. Also, the control does not drop down or match things as you type base connector names.

An export with errors will leave an adapter in an Update state, and apparently also duplicates the adapter statistics:

Scheduled connector jobs can still run when disabled, as this is no longer enforced on the Queued Connector Job Executor; A decorator to check the of the scheduler-state/connector enabled-state needs to be added/wrapped around each connector job on the ConnectorJobGenerator.

Some schema providers may create fields as single value when they are later required to be multivalue, such as the CSV connector. To do this currently, the field must be removed and re-added as a multivalue field. This may be a bit of work as the validator types available may change for some types.

Attempting to create a date relational with string priority transformation results in a "Sequence contains no elements" error appearing, and redirecting the user back to the adapter page.

The Group Target on the Multivalue.GenerateDNs UI component should be a text box, as this field is the target field against which the generated DN components will be written.