Hi @Fabio Posser ,
Thanks for reaching out to Microsoft Q&A.
When you sync work items between Azure DevOps (TFS) and Polarion via the TFS-Polarion connector, the connector doesn’t try to “guess” who’s who, you have to explicitly tell it which DevOps identity maps to which Polarion login. That mapping lives in your connector’s config (often called ProcessMapping.xml or tfs-polarion.cfg, depending on your version).
Here's the high-level approach:
- Open your connector’s mapping file
- Usually under
<connector-install>/config/ProcessMapping.xml(or a similarly named .xml/.cfg).
- Usually under
- Find (or add) the user-mapping section
- Look for a
<UserMappings>or<Users>element.
- Look for a
- Add one entry per user, for example:
<UserMapping tfsUser="DOMAIN\Fabio.Posser" polarionUser="fposser"/>- tfsUser must match exactly the “Assigned To” value in DevOps (including domain or UPN).
- polarionUser must be the exact login ID used in Polarion.
- Save your changes and restart the connector service so it reloads the mapping.
- Trigger a resync (or wait for your next scheduled sync) and confirm that “Assigned To” from DevOps now shows up under “Assignee(s)” in Polarion.
If you don’t see a <UserMappings> section in your config, or if edits don’t “take,” it usually means:
- You’re editing the wrong mapping file for your connector version.
- The connector process didn’t get restarted (so your changes never got loaded).
- There’s a typo or case-mismatch in one of the IDs.
Hope this helps!
If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.