Compartilhar via

How can I correct Link the Assigned To with Polarion Assignee(s) field suing the TFS connector?

Fabio Posser 0 Pontos de reputação
2026-04-29T05:54:02.7666667+00:00

Hi, on the example below I have the first requirement where I updated the Assignee(s) on Polarion using the Assigned To from DevOps. The second item below I create it on Polarion.

The first one is not assigned to my user on Polarion because there is no mapping between the User on DevOps and user on Polarion. There is a way to do this mapping?

Imagem do usuário

Thank you.

Azure DevOps

1 resposta

Classificar por: Mais útil
  1. Pravallika KV 15,375 Pontos de reputação Equipe Externa da Microsoft Moderador
    2026-04-29T06:21:24.3533333+00:00

    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:

    1. Open your connector’s mapping file
      • Usually under <connector-install>/config/ProcessMapping.xml (or a similarly named .xml/.cfg).
    2. Find (or add) the user-mapping section
      • Look for a <UserMappings> or <Users> element.
    3. 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.
    4. Save your changes and restart the connector service so it reloads the mapping.
    5. 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 User's imageand click on Yes for was this answer helpful. And, if you have any further query do let us know.

    Esta resposta foi útil?

    1 pessoa achou esta resposta útil.

Sua resposta

As respostas podem ser marcadas como ‘Aceitas’ pelo autor da pergunta e ‘Recomendadas’ pelos moderadores, o que ajuda os usuários a saber a resposta que resolveu o problema do autor.