cancel
Showing results for 
Search instead for 
Did you mean: 

To avoid merge namemapping if import projects

SOLVED
PorscheWen
Occasional Contributor

To avoid merge namemapping if import projects

Hi, 

 

I try to combine projects into a suite. However, projects are recorded by different members with different VM.

That means I would do lots of merge namemapping works. How could I avoid this issue? Since we all test same app in same VM environment.  Thanks for any suggestion.

 

Porsche

1 ACCEPTED SOLUTION

Accepted Solutions
Marsha_R
Community Hero

Re: To avoid merge namemapping if import projects

We solved the problem of lots of merge work by doing it more often.  We also alternated who had to do the merge.

 

Do a merge every couple of weeks.  Test the new name mapping with the master test, then when it passes, give everyone a copy of the new name mapping.  Now you are all starting from the same place again. 

 

The merges shouldn't be too bad if you keep the name mapping cleaned up as you go.

View solution in original post

2 REPLIES 2
Marsha_R
Community Hero

Re: To avoid merge namemapping if import projects

We solved the problem of lots of merge work by doing it more often.  We also alternated who had to do the merge.

 

Do a merge every couple of weeks.  Test the new name mapping with the master test, then when it passes, give everyone a copy of the new name mapping.  Now you are all starting from the same place again. 

 

The merges shouldn't be too bad if you keep the name mapping cleaned up as you go.

View solution in original post

sonya_m
Community Manager

Re: To avoid merge namemapping if import projects

Thank you a lot, Marsha!

 

Hi @PorscheWen! Does the suggestion help? 


Sonya Mihaljova
Community and Education Specialist


Limited time: Gain insights – and win prizes – with our event “Inside Zephyr”! Runs May 17-28
New Here?
Join us and watch the welcome video:
Announcements
Top Kudoed Authors