[Xsquash4Jira] The links between classic requirements and high-level requirements are no longer created when synchronisation is created

Affected version : 9.0.6 -> 12.0.0 + 13.0.0 + Jira CLOUD only (OK DC)

Observed behaviour

When a new synchronisation is created, if child tickets are associated with an epic in Jira, the tickets synchronised in Squash are not linked to their respective high-level requirements.

However, if you then modify these links:

  • delete and re-add them from the epic or US
  • add a new child ticket to the epic
  • add a new ticket linked to the epic and within the scope of the synchronisation

then the links are correctly retrieved in Squash

NOTE: This issue only affects JIRA CLOUD; on DC, the links are retrieved correctly during the first synchronisation.

NOTE2: it is possible that this error is due to corrections following the JIRA CLOUD deprecation

Steps to reproduce

In JIRA:

  • Create an EPIC ticket.

  • Associate child tickets with it (user story, task, whatever).

    image

In Squash:

  • Retrieve the tickets via synchronisation.

  • note that the links are not present in the table “Classic requirements linked to this high-level requirement”

    image

Then:

  • in Jira, add a new child ticket to the EPIC above

    image

  • remove one of the previous links and add it again

  • wait for a synchronisation cycle and note that in Squash, the links are now present (only the top two)

    image

Expected result

If a child ticket is present on the epic, then the links should be retrieved automatically during the first synchronisation

Edited by Xavier Devroedt