Exeperienced ChaRMers whats your process for changing the release date

[Former Member]

Looking for the experiences of others on how they handle changing the release date of a change in the development system when using ChaRM.

For example you have a change request, with a change document with attached transports that have changes saved to them. The transport is still modifiable and the status of the change document is In Development. The maintenance project the change document is assigned to goes live in September. A decision has been made to go-live with the change in December instead.

What is your process? Don't be shy

There are various options on how to handle this, but I would like to hear from the forum and compare the Pros and Cons of each process.

[ryan_wermager]

You should perform the following:

1. Create a new maintainence cycle within the ChaRM project

2. Create a new change document within the new maint cycle

3. Create a new ChaRM transport under that new change document

4. Reassign the tasks that are not released (modifiable) as you indicated to the new ChaRM transport

[Former Member]

You should perform the following:
1. Create a new maintainence cycle within the ChaRM project
2. Create a new change document within the new maint cycle
3. Create a new ChaRM transport under that new change document
4. Reassign the tasks that are not released (modifiable) as you indicated to the new ChaRM transport 

Thanks Ryan, lets go a little more granular on step 4.

Did you mean reassign the transport or the tasks?

- If you meant transport, when you try to merge your old transport with your new transport, you'll get an error that you cannot merge transports in different projects. If you go into the transport properties and try to assign it to the other project, you'll get an error that you cannot assign transports to the new project. If you then delete the project assignment in the transport and the attribute linking it to the maintenance project, you'll get an error that a project is mandatory. Luckily the error doesn't stop you from hitting the back green arrow and now the old transport is not assigned to a project. You can now merge the old transport withthe new transport.

- If you meant task, can you elaborate?

As for next steps, withdrawing the original change document and rejecting the original change request is now possible. You cannot withdraw a change document with a transport containing changes. Do you have any thoughts on withdrawing this change document and rejecting the change request?

[Former Member]

One other observation. If you have already performed a transport of copies and moved it to the test system, ChaRM does not let you withdraw the change document even after you merge the transport of the old change document with the transport of the new change document. There are ways to force this with reports, but I do not like using them if it can be avoided.

How do others manage this situation?

[ryan_wermager]

I meant tasks. You can reassign a task using SE10 in the development client as long as the task is not released. This means that if you want to reassociate the underlying objects or code (doesn't matter it can be customizing or workbench) to another transport inside of ChaRM or outside of ChaRM - you can do that. If you need instructions on how to do that, let me know.