Actions
Bug #2675
closed
Buttons in group screen are in confusing places
Status:
Released
Priority:
2
Assignee:
Jean VILVER
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When editing a group, the three buttons are at the bottom of the screen in this order: Clone Update Delete.
This is confusing, because:- We always have the "default" rule at the bottom right everywhere. So "Update" should be on the far right.
- In the Directive and Rule screens, the Delete button is in a separate frame at the top of the screen. I think we should do the same in this screen. The Clone button could go there as well.
Files
Actions
#2
Updated by Jean VILVER over 11 years ago
- File top_screen_actions.png top_screen_actions.png added
- File bottom_screen_actions.png bottom_screen_actions.png added
- Status changed from In progress to Discussion
- Assignee changed from Jean VILVER to Jonathan CLARKE
Jonathan CLARKE wrote:
[...]
- In the Directive and Rule screens, the Delete button is in a separate frame at the top of the screen. I think we should do the same in this screen. The Clone button could go there as well.
I tried both of your options :
1) Move Clone and Delete buttons on top of the forms:
2) Move Update on the far right, and Clone and Delete on the left:
I think it's better to put that kind of actions on the bottom. It seems common on crud apps to put them there (ie: google image : "crud apps").
What do you think?
Updated by Jonathan CLARKE over 11 years ago
- Assignee changed from Jonathan CLARKE to Jean VILVER
OK for me, so long as we have a consistent approach throughout the application: for groups, directives, rules, etc... So if you change one, please change them all! :)
Updated by Jean VILVER over 11 years ago
- Status changed from Discussion to Pending technical review
- % Done changed from 0 to 100
Applied in changeset e69af1aed721b8178fa3a1d794f85d45c1d1aede.
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Pending technical review to Released
This seems valid, thank you Jean
Actions