Bug #6165
closedIn rule details->compliance, reload should reload all graphes at once
Description
When we are looking at the compliance details for a rule, there is several "reload" buttons: one for the "Compliance by Directive" array, an other for the "compliance by node" one.
It is EXTREMELLY strange to have to have that possibility, because when we reload something, then most of the time the two arrays are desynchronized, and the recent changes is always out of date - especially when we first looked at the rule after a change.
We should have only ONE reload button that reloads the 3 graphes at once.
Updated by François ARMAND almost 10 years ago
- Subject changed from In rule details->compliance, reload should reload every graphe to In rule details->compliance, reload should reload all graphes at once
Updated by Jonathan CLARKE almost 10 years ago
- Assignee changed from Jonathan CLARKE to François ARMAND
- Priority changed from 2 to 3
I don't know why this is assigned to me, as there is no question for me to answer, and I certainly can't implement this...
Obviously I agree that this is confusing and should be fixed.
So reassigning to you, François.
Updated by François ARMAND almost 10 years ago
- Status changed from Discussion to 8
- Assignee changed from François ARMAND to Vincent MEMBRÉ
I was a UI/UX things, so yes, I wanted to have your opinion on that.
Vincent, the implementation is for you.
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/794
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset f762856ef64f2dd43236168b7d7d548ce8397d3d.
Updated by François ARMAND almost 10 years ago
Applied in changeset 8c4bbbd9dbf084136737b240b36c34e0f98c6ca5.
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0, which was released on 2015/02/16
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/