Task Under transport request

[Former Member]

Hi,

I have one of the Object under one TR and after some time I need to add one more task under that ID.

But that task is going under some one else TR .

That task is to create messages(se91) we have created one big message class .... Z*****.

Thanks

Mohinder Singh Chauhan

[Former Member]

Hi

YOu can give the same TR for your object as well..

That TR will have two Tasks one for the existing and other for ur User ID..

You can can individually release task and then ur TR.

Hope it helps.

Praveen

[Former Member]

Mahinder,

There are 2 options.

1. Ask other person to delete that task

>Go into that messege class in change mode and just press space bar(this is just for system to under stand some change happend).Now try to save it it will ask request ID .Give your request ID.

2.Ask him to release that request(Just release not to transport to quality.If he don't have any problem).

Now same like above.Do some change and assign save .assign to your request.

[Former Member]

HI,

Delete the object from the newly added request. go to the object and make any small change and try to activate it again. now it will ask for a request to select.Press F4. Select the required Request from Popup.

This should solve your issue.

Please let me know if you still face the issue.

Regards,

Li

[Former Member]

Hi,

You can add the sub tasks to the already created TR.

Ex:

You have created a TR no X and after some time you want to include one more task to

the same TR no X, for that when you are activating there will be an option 'Own Requests'.

Select that option then it will show you all the TRs created by you. then choose the TR no X.

It will automatically create a subtask in TR no X.

This will happen only when TR has not yet released.

Please reward me if it is helpful

Regards,

Jallu

[uwe_schieferstein]

Hello Mohinder

If you change a repository object like a message class the system puts the transport object into a workbench request (actually into a task of a workbench request). The repository object is locked for the request as long as the transport is not released. This means that the same repository object cannot be locked into two changeable transport requests at the same time which makes completely sense.

Thus, if 5 different people work on the same message class all there changes will be stored in different tasks of the workbench request holding the message class object.

If you are the owner of the entire transport request then you have always the authorization to change the owner of a task or release this task.

Please note that the locking mechanism is not available for customizing request. So here is a potential and frequent problem. Think about the following scenario:

(1) Developer A changes a customizing entry and saves the changes in customizing request A.

(2) Developer B changes the same customizing entry and partially reverts the changes of (A). She stores the changes in her own customizing request B because she does not know that the same customizing entry exists already in request A.

(3) Both release their request.

(4a) Request (A) is imported, followed by request (B) => result: changes of developer A are partially lost, developer B is happy

(4b) Request (B) is imported, followed by request (A) => result: changes of developer B are partially lost, developer A is happy

A similar scenario can happen with workbench requests if request (A) is released but not immediately transported into QAS and after testing into PROD and a second workbench request (B) is overtaking request (A).

Regards

Uwe