Polarion/Jira integration

Overview

Get traces of requirements and tests impacted by Agile activities

---
config:
  theme: neutral
  layout: elk
---
  graph LR
    %% Définition des sous-graphes
    subgraph Polarion
        R1(Requirement)
        R2(Requirement)
    end

    subgraph JIRA
        E(Epic)
        S1(Story)
        S2(Story)
    end

    %% Relations
    E --> R1
    E --> R2
    E --> S1
    E --> S2
    S1 --> R1
    S2 --> R2 


    %% Application des styles
    class Polarion,JIRA system;
    class R1,R2,E,S1,S2 item;

    %% Ajustement de la direction
    linkStyle default stroke:#000000,stroke-width:1px;

In an Agile project, stories and epics serve as developmental artifacts. They are instrumental in organizing sprints and are not designed to store long-term data about needs. Therefore, it is logical to link these Agile artifacts to requirements.

Tasks

Synchronize Agile artefacts

• WI.11 - Link Agile artefacts to Engineering artefacts

Synchronize change requests

• WI.06 - Create & Synchronize a Change Request with JIRA

Synchronize JIRA defects

• WI.11 - Link Agile artefacts to Engineering artefacts