Template does not always get data from labels or levels in the same order

Description

Overview:
In cases where there are two sets of enumeration (e.g. Label 1 and Label 2) and they are used by the template, then the outcome when generating the display labels/descriptions for the issues based on the template is not always the same for the same set of data input

Steps to Reproduce:

  1. Create new serial and add publication pattern

  2. In the publication pattern specify two enumeration labels Label 1 & Label 2

  3. In the template use both labels e.g. enumeration1.level1 / enumeration2.level1

  4. Preview the pieces, entering a date and different numbers for each of the Labels (e.g. 1 and 99)

  5. Repeatedly press 'Preview' and note that sometimes values come out one way (e.g. 1 / 99) and sometimes the other ( 99 / 1) even though no changes are being made

Expected Results:
The data should always be used in the same way and the outcome should always be the same

Further information

This can also happen with the level numbering. E.g. having enumeration1.level1 / enumeration1.level2. Repeatedly pressing the “Preview” button in the create predicted pieces dialogue can lead to different results - sometimes the correct levels being used and sometimes the levels being reversed

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

Activity

Show:
Done

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

K-Int

Release

Quesnelia (R1 2024) Bug Fix

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 23, 2024 at 4:25 PM
Updated April 15, 2024 at 11:58 AM
Resolved April 12, 2024 at 11:10 AM
TestRail: Cases
TestRail: Runs

Flag notifications