Note that the “View All” still has the ability to update columns but this has not been done for “By Service” and “By Host”.

Hi,

Both 23.10.11 and 23.10.12

I observe the same issu. In the view “All”, it is indeed possible to move a column, and to add one. But the column added disapears if choosing another view and going back, also, if moving one of the “lasting” column and leaving the page and going back, column order is lost too. I’ll have two questions about this:
 

1. How could it be possible you haven’t noticed this? If you did notice it, how can you consider it is acceptable to release although still are such bugs in the UI? Considered against a purely eye candy effect like the one added on the text in the About page, I don’t know what other people you think, but I, myself, am quite aghast.
2. How can you tag this report “needs votes”? Are you suggesting such very obvious design/technical issues as these ones may be fixed, eventually, only if enough peoples click on that Upvote button?
   
   
   Does the “Technical Success Manager” agreed? (Believe it or not, I can’ stop rolling on the floor laughing after I read such a marvelous job title, but at least it lessen my pain ^^… did you invented it, or am I the ignorant moron here? I’m too afraid to check it myself, as I can’t tell what would be the worst possibility between both.
   
   
    

Seven. Holy. Months

Hi all

any news regarding this request?

Can we expect to see this improvement (which I'd rather describe as a bug) one day ?
This point (among others) is a real brake on the adoption of the resource status page.
I assume that many users are still using the deprecated pages, but when they are no longer available (which seems to be getting closer, given the malfunctions that have appeared with 24.10), there's no doubt that this point will reinforce user dissatisfaction.

​@tyduch I know this is requested but I am not sure i understand in what way it is preventing transition from legacy views to resource status given those views did not have column management either. Can you please clarify?

Of course yes.

Every legacy users around me continue to use deprecated pages for various reasons.

In this case, it's the fact that the resource status view doesn't display the “Severity”, “Notes” and, to a lesser extent, “Actions” fields by default (and must be set again each time the cache is cleared).

But there are some others, for example :

• difficulty getting used to the new filter system
• disturbing links from custom views: you don't arrive at a filtered view of the chosen host or service, but at the view with the last filter used (which may have no connection with the desired item) and the detail pane open on the right, dealing with the desired host or service.

Thanks for those details. Saving preferences in the database vs in the browser cache is planned. There have been improvements in filtering in the past versions, what version are you using? As for links from custom views that has not been addressed but the new dashboards do open resource status in the context of a click (either a filtered list or the detail panel if this is one specific resource).

Hello,
Sorry I did not found time to answer you before.

Good news if an evolution is planned for preferences. Can you tell me when it should be delivered ?

Regarding the version we are in 24.10.4.

As for links from custom views will it be add in your roadmap or should I have to open a specific thread for that ?

Thanks for your help