[Feature Request] "stickify" the second button row

[g00fy]

While I'm submitting FR's here, I will add this (small) nuisance too:

I have it a lot that tickets which doesn't belong together come from several people seperately and I want them to be grouped. Thus I need to click the "more >>" link and click "merge". This works perfect. But my screen is big enough to always show all the buttons.

Is there a possibility to "stickify" the "more >>" to be always open (for example when you click "more >>" it opens and changes to "less <<" while setting a cookie to keep it open even the next time you browse to the helpdesk?


Thanks

[dfroberg]

+1

Very good idea

[Hildy]

cerb4/plugins/cerberusweb.core/templates/tickets/ticket_view.tpl.php, line 206. Change<div id="view{$view->id}_more" style="display:none;padding-top:5px;padding-bottom:5px;">to<div id="view{$view->id}_more" style="display:block;padding-top:5px;padding-bottom:5px;">

[g00fy]

I know ;), that's about how I do it now, but it would be nice to have it in the official distro.

[jstanden]

Sure, we could persist the state of the 'more >>' div in the Worker Preferences rather easily.

http://www.wgmdev.com/jira/browse/CHD-424

[g00fy]

It would be good if the state would get saved in some configuration table (as opposed to the cookie variable).

[jstanden]

Yeah, the "Worker Preferences" I mentioned above is a database-backed registry we use in the code. It caches in the current session but it will persist forever.

Similar things happen for the global settings or group settings. It's much nicer, and more plugin friendly, than creating a database field for every possible option.

[g00fy]

You're talking about the "CerberusSettings" registry class right?

[jstanden]

There are several registries in Cerb4:

DevblocksExtension::setParam()
CerberusSettings::getInstance()
DAO_GroupSettings::set()
DAO_WorkerPref::set()The 4th one would be the most applicable in this case.

[g00fy]

ok :-) thanks for teaching!

[jstanden]

Anytime! Thanks for caring. ;)