In test asset duplication - where do the project areas comes from ?
When you go to duplicate a test asset, it offers you up a list of alternative project areas. I was wondering where those project areas come from, and in what deployment scenarios this would still work.
So the question I have is
1) if you had linked JTS's - would it pick up RQM projects on the remote JTS ?
2) if you had multiple RQM servers - but with common JTS - would it pick up projects on the other servers ?
3) is it just projects on the current server ?
Any help much appreciated
Thanks
Steve
So the question I have is
1) if you had linked JTS's - would it pick up RQM projects on the remote JTS ?
2) if you had multiple RQM servers - but with common JTS - would it pick up projects on the other servers ?
3) is it just projects on the current server ?
Any help much appreciated
Thanks
Steve
One answer
Hi Steve,
So to answer your questions in order:
1) No. If you have a linked JTS, it would not pick up RQM projects
2) No. If you have multiple RQM servers but with a common JTS, the project areas are not shared between RQM instances
3) Yes. Basically when you duplicate a test artifact you will be only be presented with Project Areas that the current user is a member of (has adequate permissions) on the current RQM server.
So to answer your questions in order:
1) No. If you have a linked JTS, it would not pick up RQM projects
2) No. If you have multiple RQM servers but with a common JTS, the project areas are not shared between RQM instances
3) Yes. Basically when you duplicate a test artifact you will be only be presented with Project Areas that the current user is a member of (has adequate permissions) on the current RQM server.