Actions
Bug #14859
closedThe "migrate" field should not be displayed on directive creation
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
56
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
When we create a directive based on a technique for which several version are available, we must hide the part of the form with "migrate" and only display the current technique version.
If the user tries to change version during creation ("oups, I wanted to use the previous technique version"), whatever he does will fail:
- changing the version and hitting "save" will just not change the version,
- changing the version and hitting "migrate" leads to a blank edition zone (certainly an error when the form tries to find information from a not yet existing directive).
Actions