While there is a work-around to control the time a 24hr job runs by creating the job near the desired time, it would be a better user experience if this were to be a preference setting in the job details.

This is now achievable with the release of the Automation API that Gearset has released. Please see the documentation on https://docs.gearset.com/en/articles/6341493-getting-started-with-the-gearset-automation-api

It would be helpful if we have some level of predictability about when the job would run, especially if they are on a 24 hour schedule. Alternatively, please do allow us to trigger them manually through your API. For example, we can run a script from Azure devops that is scheduled.

I understand no time for 1 and 4 hourly jobs, but if someone only wants a deployment every 24 hours, it makes sense to specify a time. We would like to do a deployment every night after hours once all developers have finished for the day and testers in the sandbox are not impacted during the day. Currently, regardless of when we start the jo, it runs at 1:17PM AEDT. Presumably out of business hours for the US/UK.

I think this is an important function to stay up with other CI/CD Deployment Tools. You need to still have a little control over timing if needed. Even for resource purpose the job could kick off within the hour schedule i.e if you select 1pm every Tuesday and Thursday it would just kick-off sometime in that hour.

This is needed for Production CI Jobs, these need to be a little more control over date and time. Example if I want to release everything on Tues, Thursday at 3pm. How it is now is fine for other sandbox orgs.

Add the ability to use a cron string or some other mechanism to control exactly what time CI jobs run rather than just every four or 24 hours after the CI job is created.