Commit changes using AES

[BijoyDeb]

Hi All,

We have created a custom scope from AES and working on sprint stories to modify the app according to business needs. We need to make sure that we are developing the solution and are moving the code to QA so sprint can be completed on time.

  When I am committing the code via AES, I do follow below approach 

1. Commit changes for update sets (stories which are dev complete)

2. Publish the app

3. Install latest version in QA instance

4. Manage stashes in dev

When I do this, i noticed that the updates that I haven't committed (stories not dev complete), those also get applied to QA instance which I don't want

Am I doing something wrong?

Can someone please guide me in detail what happens with each thing, as I'm doing for this 1st time.

Thanks 

[Jeroen Kopczins]

Hi BiljoyDeb, 

Sorry to hear you accidentally moved some of your work over to another instance which you didn't want. Everything that you develop for a custom application, will be captured in an application scope. All of the development will then be published with the newest version unless you've manually told the system not to do so. This means that once you installed the application it took everything, including the unfinished work/ stories. 

In application development you only use update sets in case you do development out of the application scope. 

Normally you only publish and install custom applications, like those you made in AES when you're "done" with a certain release. You can compare it to the app store on your phone. You (normally) also don't install apps or versions of an app, that are considered "in development" 

I hope this helps!