Actions
Bug #18685
closed
Techniques not correctly loaded right after upgrade to 6.2
Status:
Rejected
Priority:
5 (lowest)
Assignee:
Category:
Web - Technique editor
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
I had a technique with one param and one ressource
After upgrading to 6.2, first visit to technique editor shows an empty technique editor
Second shows the technique but without param not ressource
Third visit shows the technique
Yet, clicking on the technique (that is currently shown) display the nefarious "Unsaved changed technique"
Files
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 805 to 6.2.0~rc1
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.2.0~rc1 to 6.2.0
Updated by François ARMAND about 4 years ago
- Priority changed from N/A to 1 (highest)
Updated by François ARMAND about 4 years ago
- Priority changed from 1 (highest) to 5 (lowest)
We tested with last nightlies, with at least ubuntu 20, centos 8, sles15 and we weren't able to reproduce that. So either it was corrected since RC1, or we didn't find the correct context in which it happens.
As it is at least not systematic (even rare ?), I would say it's not a blocker.
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Technique editor - UI/UX to Web - Technique editor
Actions