We’re moving our transport of copies to QA for our project. Each normal change contains multiple transport requests. If errors are encountered during the transport move I switch the ZMMJ back to “In Development”, assign a new transport request (to fix the error), and then pass it back to test. This creates another transport of copies for all of the transport requests assigned to the ZMMJ, even though there is nothing wrong with the original transport of copies (which in most cases has not yet been imported to QA). Is there a way to avoid this so that we don’t have so many unnecessary transport of copies? When I possible I do use the New Test Transport button, but there have been a few occassions when this did not work and I had to pass the ZMMJ back to test to have a new transport of copies generated.
Thanks,
Shawn