Actions
Bug #2404
closed
update group container in an existed group
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
I have created a group named "ZZZ1 - users" and after I would like to change it to a new created group category named "ZZZ1"; so I click on the group "ZZZ1 - users" change the group container and I click on update. => no change
so I click on the group "ZZZ1 - users" change the group container, click on search and I click on update. => no change
after each "click update" I make a new test like click on "search nodes" and click on "groups" just in case.
Updated by Jonathan CLARKE over 12 years ago
- Priority changed from N/A to 1 (highest)
- Target version set to 2.3.7
Er, why has this bug not been addressed!?
Updated by François ARMAND over 12 years ago
- Status changed from New to In progress
Updated by François ARMAND over 12 years ago
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Applied in changeset 2e1b7f8571c75b760ca0c811ac6982a855c5a42b.
Updated by Jonathan CLARKE over 12 years ago
This one should be reviewed by Nicolas, but he's on holiday and we need it sooner.
So, I've taken a look, although I'm no Scala expert, I can confirm that:- This commit is clean, and doesn't change anything that looks suspicious
- The updateGroup method that was changed is not used anywhere else in the code, so this shouldn't break it
- Functionally, using the application, this now works as expected
So AFAICT, this is good.
Updated by François ARMAND over 12 years ago
- Status changed from Pending technical review to Released
Actions