I think it's possible to achieve what you want in a slightly different way.
I find that asking my testers to complete their tests in Excel an easier/quicker way to get tests into ZS. You could then have an Excel template that has 40 columns for your features to test, and ask the testers to select which are primary, secondary and tertiary, adding, say, P, S, T into the relevant column but ideally P[ ], S[ ], T[ ] where [ ] = the feature number, so P1, S12, T39 (or whatever works for you of course, it could be text like P_Browser, S_Login, T_Permissions).
Using Excel you can concatenate a string to then populate into a custom field in your test case, e.g. "Features to test" which is a single line text field, and then you'd be importing something like "P1, S12, T39" or "P_Browser, S_Login, T_Permissions".
With that data now in your test case in 1 custom field, you have the 3 priorities listed, and you can create a filter in the Test Case library to view all tests that relate to P1 or P_Browser, etc.
Does that make sense?
Yes MisterB, it makes sense from a logical point. However the idea of using a mixed set of tools like that will be problematic for training a cross-continental team.
It sounds like I will have to type the same info into each of the three fields to populate them, not cloning or copy/paste. And do the same (but with a different data set) in triplicate for each of the other projects. I feared that was going to be the case, but was hoping for another way. Oh well, such is life.
