Post date: Oct 25, 2016 9:50:37 AM
If every developer in a team wants to migrate the same Triniti patch with their individual tickets, lot of time is getting wasted i) in order to upload the same patch to all tickets and ii) moving tickets from Code commit state to invoke migration.
TRI2 has one functionality as Copy objects in Attach Solution Objects frame which is already being used by our active clients (Eg: SunPower).
Copy objects functionality is useful for copying objects from one ticket to another.
Please follow Copy objects from one ticket to another ticket video tutorial to know about Copy objects functionality.
Let's take a scenario to know, how to use this functionality:
Let's say 4 developers from same team(Eg: TRI2 team) want to commit their respective code to repository and want to migrate same patch(TRI2 Patch).
Please follow the below steps:
#1) Let all the developers commit their code to repository properly(by taking all previous updates) one after the another.
#2) Any one of team (Eg: Developer1) needs to build Triniti patch from skota machine.
#3) Developer1 needs to upload patch to his/her ticket using Attach Solution Objects frame and save the object details into database for his/her ticket(Eg: IS01234 is ticket number)
#4) Now all other developers can map the same patch to their tickets using Copy Objects functionality by providing IS01234 issue number in Copy Objects tab instead of uploading same patch again.