-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Low
-
None
-
Affects Version/s: 10.97.2
-
Component/s: REST API
-
None
-
1
-
Severity 3 - Minor
-
No
-
None
Issue Summary
The customer had previously spoken to someone in Atlassian and confirmed that field IDs should be the same across instances. Can you confirm that the ID's for default shirt sizes in your instance match what we have recorded:
X-Small: 6,
Small: 7,
Medium: 1,
Large: 2,
XL: 3,
XXL: 4
If not, they would be hoping to fix it since there's no way to retrieve the associated size by ID (unless there's an API endpoint we're unaware of?)
Challenge The customers have no way of knowing what each number indicates when they retrieve a feature or epic, so they have to check it manually.
Steps to Reproduce
- Step 1. Enable T-Shirt sizes for Features
- Step 2. Set a T-Shirt size to one Feature
- Step 3. Make an API request to retrieve that feature at "/rest/align/api/2/features/<id>" and examine the T-Shirt size number
- Step 4. Go to Administration -> Platform -> Portfolio -> Estimation Conversions and change the title of one size
- Step 5. Repeat step 3, and the ID should be different

Additional Test:
1) Created a new T-shirt size field and confirmed the ID is 27, changed the name again, and ran API again, and the Number is not changed on API but still shows 27.
2) Deleted the field and Created again, and confirmed the ID is 28
3) Deleted the existing T-shirt size – small (which is the ID is 2), created the new Small T-shirt field, and confirmed ID is 29.
Result: the ID number is increased incrementally.
Expected Results
T-Shirt ID should be fixed. (For example, if the customer accidentally deletes the small size (which is ID is 7), the ID number is changed when the customer recreates it. The customer wants to keep the same number.)
Actual Results
the ID number is increased each time incrementally when recreated.
Note: The customer mentioned they have spoken with both product and engineers when designing integration stage, and Atlassian confirmed field IDs should be the same across instances.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
- relates to
-
ALIGNSP-10260 Loading...