Bug #2678
closed
After cloning a group, changes made are not saved
Added by Jonathan CLARKE about 12 years ago.
Updated about 12 years ago.
Category:
Web - Nodes & inventories
Description
When I clone a group, I first get a popup to change it's name, which I do, then I come to the standard edit group display.
However, whatever I change on this screen, when I click "Update" I get a "Success" popup, but when reloading groups, the changes to criteria haven't been saved, and the group always defaults back to "static" even when the cloned group was dynamic.
- Status changed from 2 to In progress
Jonathan CLARKE wrote:
When I clone a group, I first get a popup to change it's name, which I do, then I come to the standard edit group display.
However, whatever I change on this screen, when I click "Update" I get a "Success" popup, but when reloading groups, the changes to criteria haven't been saved, and the group always defaults back to "static" even when the cloned group was dynamic.
I can't reproduce this bug, can you try it again ?
Jean VILVER wrote:
Jonathan CLARKE wrote:
When I clone a group, I first get a popup to change it's name, which I do, then I come to the standard edit group display.
However, whatever I change on this screen, when I click "Update" I get a "Success" popup, but when reloading groups, the changes to criteria haven't been saved, and the group always defaults back to "static" even when the cloned group was dynamic.
I can't reproduce this bug, can you try it again ?
To reproduce this bug :
- Clone a group
- Change its status from static to dynamic (or opposite); or change its name
- Click save
the group will be updated, but the tree wont be
- Status changed from In progress to Pending technical review
- % Done changed from 0 to 100
Nicolas CHARLES wrote:
To reproduce this bug :
- Clone a group
- Change its status from static to dynamic (or opposite); or change its name
- Click save
the group will be updated, but the tree wont be
It doesn't seems like the bug describe in the description (or the title).
But yours, Nicolas, is fixed in c9dac4b496705af6e7160db802f47e6f04bcc5d0.
I think we should see with Jon if the bug he's describing is still there.
- Status changed from Pending technical review to Released
This bug is now fixed, thanks Jean.
Also available in: Atom
PDF