Can I map TF planning folders to multiple requirement types?
Yes, you can, but you have to carefully read the following explanations: If you map TF planning folders to multiple HP QC requirements, the entity service has to determine for every single project mapping whether to update or create an artifact. If the TF planning folder has been created by CCF, the identity mapping table already contains an entry for the reverse direction (TF PF to requirement type) as well. Consequently, the entity service will correctly identify the corresponding requirement and will do the update. Unfortunately, this will not be the case for all other TF PF to requirement type mappings: Since no mapping is present, new requirements would be created. To prevent this from happening, you may create an XSLT rule that only passes artifact updates and resynch requests but no creation or deletion requests.
