Wow! This is nice looking and much more functional for average users. Is this still based off RT3 code, or have you based it off the 4.x series? Also, are there any plans to make your changes available for public consumption?
-- Gary L. Greene, Jr. Sr. Systems Administrator IT Operations Minerva Networks, Inc. Cell: +1 (650) 704-6633 > On Mar 31, 2016, at 8:44 AM, akos.to...@docca.hu wrote: > > Hi Vegard, > > We had a plan for a similar goal: > http://lists.bestpractical.com/pipermail/rt-users/2014-March/083068.html > <http://lists.bestpractical.com/pipermail/rt-users/2014-March/083068.html> > > We had and have not enough knowledge to use the new REST interface, so we > couldn't reach the original goal, but we made a lot of small ajax > implementations: > > - we have a Results.html with all the fields is editable in the ticket list, > so the user could modify all the data (the columns) without > clicking-getting-diving into the ticket, and diving deeper into the > particular sub-page or jumbo (basics, dates, etc). > <ajax editable ticket list.png> > > - a TicketSimple.html, just the necessary data > > - we've changed the Ticket.html header, almost every field (custum and > default) field is ajax editable, no need to move to jumbo or so. Like this: > <Ajaxed Ticket.png> > > > > > These are running on RT3.8, some of them on 4.2, we don't know yet how those > work on 4.4. > > We don't know if our coding style and quality is okay for RT or not, and we > are not familiar how to share this plugins on github or so. So we use these > in house, but we could give you access to our test system, you can try it, > and if you find useful we could send you the code for 3.8 (and the 4.2 as > well but it is not in everyday use). > > Bests, > > Ákos > > On Thu, Mar 10, 2016 at 2:36 PM, Vegard Vesterheim > <vegard.vesterh...@uninett.no <mailto:vegard.vesterh...@uninett.no>> wrote: > Some of our users find the RT web gui complex, and also ineffective for > some use-cases. I have been tasked to investigate alternative GUIs > for RT. > > The "criticism" relates to the fact that some fields are irrelevant for > some users and should be possible to suppress, and also that the default > ticket display does not allow editing the fields directly. We are > considering creating a new ticket display page which combines the > contents from Basics (Ticket/Modify.html) and History > (Ticket/History.html). This is fairly easy to implement, I guess. Maybe > one could even add a user preference for default ticket display page. > > BTW, I am aware of the Jumbo option, and I also know that the latest > version (4.4) can suppress display of unused fields. The mobile UI is > also a possible solution to the complexity concern. > > My questions to the list, however, are of a more general nature: > > Has anyone considered/implemented/used any alternative GUIs for > manipulating RT tickets? > > -- > - Vegard V - > --------- > RT 4.4 and RTIR Training Sessions > (http://bestpractical.com/services/training.html > <http://bestpractical.com/services/training.html>) > * Hamburg Germany - March 14 & 15, 2016 > * Washington DC - May 23 & 24, 2016 > > --------- > RT 4.4 and RTIR Training Sessions https://bestpractical.com/training > * Washington DC - May 23 & 24, 2016
signature.asc
Description: Message signed with OpenPGP using GPGMail
--------- RT 4.4 and RTIR Training Sessions https://bestpractical.com/training * Washington DC - May 23 & 24, 2016
