The most prominent way to convert corrupt OST file into PST format is ATS OST to PST converter software. It is very trustworthy so you can trust on this for converting the data of OST mailbox along with all properties mailbox, inbox, journals, task, calendar, contact, sent items, junk mail, attachments, and etc. this software supports all version of windows up to latest Win8.1(32 and 64 bit). And MS Outlook version (97, 2000, 2002, (XP), 2003, 2007, 2010, and 2013 (32 and 64 bit).

Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.

Switching to dotnet fsi will allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/

Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.

When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.

Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.

Optionally provide a friendly interface (date picker control) for the respective values.

Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
This is not possible now, the only solution now is to cancel all the existing tasks.

When deploying to c:\mydirectory#{Octopus.Release.Number} Runbooks are unable to obtain the #{Octopus.Release.Number} information from the deployment. Which makes a lot of actions rather difficult.
If it was possible for a deployment to set a variable available to Runbooks or for Runbooks to query information in releases per environment that would really be great.

Streamline data entry

Given an JSON settings file which has an array element

e.g. { "Users": [] }

Use Octopus variables to insert into the array rather than just replace values.

e.g.
define Users:0:Username = user
define Users:0:Password = password

Would result in the object getting inserted

{ "Users": [ { "Username: "user", "Password": "password" } ] }

https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7

The idea is to have the tenant variables displayed vertically, with one column for each environment.
Currently, it is quite tedious to compare or copy variable values from an environment to another.

In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.

Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.

Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

It would be great if you can persist the state of excluded steps to the next environments as part of same release?

As per - https://help.octopus.com/t/deploy-a-release-accessing-variables-from-last-release/22788

You should be able to access a previous releases Step output variables, for when a release has already been deployed.

Either via the Deploy a release step.
Or more generally to retrieve these values for a given release.
E.g. an obtain Release information step

The deploy release step assumes want to deploy to the same environment as the parent deployment.

Add facility to pass a parameter to chose which environment to deploy the release too.
E.g. so can deploy a single master release, which kicks off multiple deployments of other release to the defined environments specified by the parameters.

Similar to how the community Chain step template allows for.

We deploy our packages to our customer environments.
For example 1.5GB of packages to 500 targets over the internet. As the internet connections can be slow and to make sure that the deployments all take place at the same (scheduled) time I suggest that the "acquiring packages" step optionally starts as soon as a deployment is scheduled and verified again at the scheduled execution time. Should the deployment package(s) be missing or corrupt at the scheduled execution time there could also be an option "re-aquire at execution"/"fail if missing".

Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.

Our use case:
We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.

Our current fix:
Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning