Over the past few weeks, I’ve been spending my time putting together an initial implementation of a modern phone-friendly interface for RT.
We’ve just published the source code to http://github.com/bestpractical/rt-extension-mobileui and it will show up at http://search.cpan.org/dist/RT-Extension-MobileUI in the very near future.
This is very much an initial release and I know there are things that need improvement, though I’d greatly appreciate feedback to help figure out what those improvements should be.
We’ve tested this new UI on the iPhone, Android 2.x, BlackberryOS 4.5 and 5.0, Kindle 2.5 and in a number of desktop browsers.
Once you install the extension, you can have a look around from your desktop browser by visiting /m on your RT server. The Mobile UI tries pretty hard to detect mobile browsers and push them to the mobile login page, though there’s a link to get back to the full UI if it gets your browser wrong.
Right now, the mobile interface supports:
- External Authentication
- Regular RT Login
- Creating Tickets
- Search (using the same “Simple Search” as the main UI)
- Display of saved searches
- Ticket display
- Ticket comment/reply
- Ticket history
- Attachment download
More screenshots after the cut
Comments
9 responses to “RT for mobile devices”
Fantastic – thanks! I’ve been wishing for something like this for a while.Graham
Wonderful news!
Great Work! Thanks Jesse, Thanks BPS.
@RichT – Try out 0.95, we’ve fixed a couple of prefix bugs for folks running RT places other than /
Howdy, nice work thank you! Certainly detects iPhone without a problem.After logging in it redirects to http://domain.com/m
But my RT is running in http://domain.com/rt3
How can I change this?
Thanks Jesse! It now works for RT in places other than /But I did still have to edit /opt/rt3/local/plugins/RT-Extension-MobileUI/html/m/login to get mobile login working.
I had to change the form action:
from action=”<% $form_action %>“
to action=””
I’m new around here so sorry to post here if this is not the right place.
Here’s one (hopefully simple) enhancement request — in the ‘unowned tickets’ screen, it would be great if there was a ‘take’ option….
I have just implemented this and at first blush, I think it fits the bill very nicely. The only think I see right off that is somewhat challenging for us, is that we have a few custom fields in our create tickets form that are important, but not available via the mobile interface, although they do actually show up when I view the ticket. I’ve glanced at the HTML a bit, but not being a perl guy, I’m as likely to break it as anything. How hard do you think it would be to add custom fields to the create ticket window? If this is something I would need to do just for my instance, what might the code look like as a basis to start from?Thanks. This is very nice work!
Sean
Greetings,A coworker pointed me at this, and I took the 5-10 minutes it took to install it with our current 3.8.2 instance. It seems to work at least partially, even on my Palm Pre (not listed in your tested smartphones). Though I do have a problem when I try to look at an individual ticket – I get the following error:
could not find component for path '/Ticket/Elements/ShowPriority'Is this just an artifact since I’m running an old version of RT, or…?