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).
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.10 to 5.0.11
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.11 to 5.0.12
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.12 to 5.0.13
- Priority changed from 61 to 60
Updated by Vincent MEMBRÉ over 5 years ago
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 60 to 59
Updated by Vincent MEMBRÉ about 5 years ago
- Target version changed from 5.0.14 to 5.0.15
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Priority changed from 58 to 56
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/2609
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b16d4ce214d04c76a5d93f517a4ed773f296fbcd.
Updated by Alexis Mousset about 5 years ago
- Subject changed from Directive creation must not display the "migrate" field to The "migrate" field should not be displayed on directive creation
- Name check changed from To do to Reviewed
Updated by Alexis Mousset about 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions