Problems with different charm correction scenarios (UC)

[Former Member]

Hi!

We tested some ugent-correction scenario.

Scenario 1:

In our scenario we have a development which was imported in QA with RC=8.

Then we went back to development and crated a second transport request in which we did correct the error.

While importing the second time both transport request have been imported in QA.

But unfortunately the development was not activated with the new version in QA.

We do find the old version activated in QA and in version history the new modif has been there, but not activated.

Why does the activation not have been done automatically in QA?

Scenario 2:

We do have some developments which normally should be imported with "unconditional mode".

How can we do that with ugent-corrections within charm?

Scenario 3:

Transport is imported in QA.

How can I reimport the transport request again?

Thanks for your help in advance.

Regards,

Alex

Edited by: Alexander Barth on Nov 30, 2009 7:00 PM

Edited by: Alexander Barth on Nov 30, 2009 7:00 PM

[former_member385033]

Hi Alexander

to question 3: If you work with transaction type SDMJ all Ur gentCorrections will be imported at the end of the release cycle. Otherwise you have to use STMS. ChaRM does not have an option to re-import an already imported UrgentCorrection.

Holger

[former_member385033]

Hello Alexander,

the answer to Scenario 1 is probaly not really related to Change Req Management, please try to import these 2 transports using STMS in the satellite system, you will probably get the same result.

Scenario 2: We assign the change document (UC) to an IT operator, which is executing the import it manually and the reassign the document back to the Tester/Developer.

Best Regards,

Holger

[Former Member]

Hi,

any idea?

Regards,

Alex