Issue #10433 has been updated by Daniel Pittman. Status changed from Unreviewed to Needs Decision Assignee set to Nigel Kersten
I have updated the ticket to send it over to our product manager for further thinking and, ultimately, to get this into the pipeline to get those decisions made. This isn't going to lead to a quick change, though, because it is really the tip of the iceberg around better user experience in the dashboard - and so is likely to wind up being resolved as part of a substantial push to solve many of the pressing issues there. ---------------------------------------- Feature #10433: Reporting change categories https://projects.puppetlabs.com/issues/10433 Author: Matt Goebel Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: Target version: Affected Puppet version: Keywords: Branch: I use the dashboard to monitor system changes. Some changes I care about, some are completely trivial and I don't really care to know about them. Simply reporting a system as "changed" makes it very difficult to sort out what's what. I would like to see a few change "categories" if you will that I could define per resource. So instead of just having changed on the dashboard you'd have something like changed - critial/normal(default)/trivial etc... User defined categories in addition to some default ones would be the ideal. This is slightly related to #7555 although no reporting is not what I'm asking for here. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
