Do​ ​you​ ​use​ ​multiple​ ​Polarion​ ​servers?​ ​Do​ ​you​ ​work​ ​with​ ​customers,​ ​or​ ​partners​ ​that​ ​also​ ​use​ ​Polarion? Are​ ​you​ ​spending​ ​time​ ​manually exchanging data with other teams, customers or partners? ​If so, traceability must be a real issue and the Polarion Connector is for you.

Polarion​​ ​Connector​ ​for​ ​Polarion®​​​ ​seamlessly​ ​connects​ ​your​ ​cross-functional​ ​teams​ ​by​ ​enabling bi-directional​ ​synchronization​ ​of​ ​work​ ​items​ ​between​ ​different​ ​Polarion​ ​servers.​ ​Thanks​ ​to​ ​a​ ​direct integration,​ ​disparate​ ​teams​ ​can​ ​collaborate​ ​right within ​the tools they're used to working with.

Polarion​ ​Connector​​ ​​for​ ​Polarion®​​ ​within​ ​​Polarion®​ ​SYNCHRONIZER​™​,​ ​lets ​ ​you​ ​seamlessly​ ​integrate​ ​disparate​ ​applications​ ​with​ ​Polarion’s​ ​unified​ ​ALM​ ​Solution.​ ​It​ manages​ ​all​ ​integrations​ ​centrally​, ​to​ ​speed​ ​up​ ​development​ ​and​ ​maintenance by letting you connect ​all​ ​integrated​ ​applications and ​eliminate​ having to ​interface​ ​with​ ​them individually.

Here​ ​are​ ​some​ ​scenarios​ ​where​ ​​Polarion​ ​Connector​​ ​​for​ ​Polarion®​ ​can​ ​help:

  • You​ ​have​ ​one​ ​server​ ​for​ ​the​ ​engineering​ ​team​ ​where​ ​your software​ ​is​ ​developed​ ​and​ ​validated,​ ​and another​ ​server​ ​for​ ​the​ ​product​ ​and​ ​project​ ​management​ ​team​ ​where​ ​requirements​ ​are​ ​written and​ ​managed.​ ​Polarion​ ​Connector​​ ​​for​ ​Polarion® ​give​s ​your​ ​engineers​ ​direct​ ​access​ ​to​ ​all​ ​requirements,​ while ​giving your​ ​project​ ​managers​ ​direct​ ​oversight​ ​of the development​ team's progress.

  • You​ ​have​ ​a​ ​project​ where development is ​outsourced​ ​abroad.​ ​You​ ​don’t​ ​want​ ​to​ ​give​ ​the development​ ​team​ ​access​ ​to​ ​your​ ​main​ ​Polarion​ ​server,​ ​but​ ​you​ ​want​ ​them​ ​to​ ​see​ ​the requirements​ ​they​ ​need​ ​to​ ​implement.

  • You​ manage customer​ ​requests​ ​on​ ​a​ ​Polarion​ ​server.​ ​Your​ ​customers​ ​have​ ​access​ ​to​ ​this server,​ ​post​ ​questions​ ​and​ can view​ ​the​ ​status​ ​of​ ​their​ ​requests.​ ​You​ ​use ​a separate​ ​server​ ​for​ ​​​development​ ​and​ ​project​ ​management​.​ ​You​ ​want​ ​your ​teams​ ​to​ ​see​ the customer requests,​ ​but​ ​you​ ​don’t​ ​want​ ​the​ ​customer​ ​to see​ ​your​ ​internal​ ​details.

  • You​ ​have​ both a​ ​public​ ​​and​ ​a​ ​private​ ​server and​ ​want​ ​to​ ​synchronize​ ​data​ ​between the​ two while keeping your private data private. ​

  • You​ ​are​ ​working​ ​with​ ​a​ ​partner​ ​that​ ​uses​ ​Polarion.​ ​You​ ​want​ ​to​ ​synchronize​ ​your​ ​requirements with them and receive their status updates.

Here's a closer look at a use case with ​two​ ​Polarion​ ​Servers:

  1. The​ ​first​ ​Polarion​ ​server​ ​is​ ​for​ ​requirements​ ​​​and​ ​QA​ ​management.​ ​Let’s​ ​call​ ​it Polarion​ ​REQ-QA.

  2. The​ ​second​ ​server​ ​is​ ​for​ ​development.​ ​Let’s​ ​call​ ​it​ ​Polarion​ ​DEV.

You​ ​want​ ​to​ ​synchronize​ ​​​User​ ​Stories​ ​and​ ​Defects​ ​to​ ​the​ ​​development​​ ​server​ ​so​ ​that​ ​the development​ ​team​ ​knows​ ​what​ ​to​ ​implement. You also want ​the​ ​status​ ​of​ ​these ​User​ ​Stories​ ​and​ ​Defects​ ​synchronized with the requirements​​ ​server​ ​so​ ​that​ ​the​ ​Product​ ​and​ ​QA​ ​teams​ ​can​ ​monitor​ ​the​ implementation ​status.

With​ Polarion​ ​Connector​​ ​​for​ ​Polarion®​ ​these​ ​User​ ​Stories​ ​and​ ​Defects​ ​are​ ​synchronized​ ​seamlessly, with​ ​all​ ​changes​ ​to​ ​your​ ​items​ ​propagated​ ​to​ ​the​ ​other​ ​server​ ​automatically.​

(A single, traceable source that's maintained on both servers.)