on 06-23-2015 1:25 PM
Hi Guys,
We have implemented CHARM for our ECC landscape.
While using the normal change we are having one issue.
When the NC is in status " To be Tested" then TOC are in Q system and original TR is still in D system and is changeable.
What users are doing is they are creating new tasks under the original TR when status of NC is " to be tested".
Is there a way to stop creation of tasks when the status is " To be Tested" and should only be allowed to add more task under the original TR when the status of NC is " In Development"
Regards
Abhishek
Hi Abhishek,
You also have to restrict authorizations for creating TRs/tasks on development system. Otherwise developers will be able to create tasks directly on the dev System as this is not restricted by the project status switch settings.
Regards
Christian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Abhishek,
This can be restricted by disabling the button for "creating tasks" in the status "To be Tested".
However, usually, when NC is under unit testing , it should be permissible to add new tasks, in case some new requirement is identified as result of that testing, or another developer has to be added.
Also, developers will still be able to create new transports , even if task creation is restricted.
Regards,
Shaswat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.