Hi Venkatesh,

You can do it with LifeTime.

In this case you will start a deployment from Test to the next environment, see image below (in my case from TST to Acceptance):

And on the screen to select the applications of your deployment plan you can change the destination environment in the arrow right next on the target environment:

In your case you will select Development.

Unless Test is the last environment of your pipeline. In that case, you should start from this option on your last environment (in my case Production 2):

Hope it helps.

Kind Regards,
João

Thanks Joao and Pramod for your quick response, actually the change what I made was little complex in higher environment. So the only way to get the changes without affecting the current progress is doing manually right?

Thanks,

Venkatesh S

Hi,

i've never done any of this, so don't know if this is ridiculous, but what would happen if a developer opened the current dev version in service studio, then the prod version gets migrated back to the dev version, overwriting all dev changes, keeping only your hotfix changes on the server.

And then, after that, developer clicks one-click-publish, OS detects version difference and offers it's usual merge tool to help bring both versions in line.  Would that work ?

Hi Venkatesh,

Another way of doing this, e.g. when the changes are quite local, is to open the module from Devthat you want to do the changes in in Service Studio. Then switch the environment to the Test environment. Here you can merge the changes you need from the published version. After merging, switch the environment back to Dev.

Good luck!