We’ve recently deployed a few updates to Lighthouse:
- Ticket Previews
- Message Notifications
- Sortable Columns in the Ticket Listing
as well as some minor improvements. For more details, continue reading.
Ticket Previews!
A much-requested feature in Lighthouse, you can now preview the formatting on your tickets before posting. We’re also working on adding this to Messages and Pages.
Message Notifications
We’re working on improving Lighthouse’s Messages feature. The first in a series of improvements is notifications. Like with Tickets, you can now choose people to get email notifications when a Message is posted or a comment is added to the message. You can also reply to these emails to reply to the message. This is a great way to communicate about things that don’t need responsibility and state tracking.
Sortable Ticket Columns
Click on any header in the ticket listing to sort by that column. Click again to reverse the sorting. The arrow will indicate which column the tickets are sorted on, and in which direction.
File Upload Quota Messages
If your account has gone over its Attachment Quota, account members who are not admins will now see a message explaining why they can’t upload files.
Multiple Ticket Modification Commands in Ticket Emails
In your replies to ticket emails, you can use keywords like [state:open responsible:"Matt Lyon"] to modify your ticket. Previously, if your email had multiple sets of brackets, only the keywords in the last set of brackets were used. Now, any valid keyword inside a set of brackets are used.
Loading tweets…
Our Products
Our Open Source Projects
- astrotrain – simply the best email processing solution out there.
- Seinfeld – automatic tracking of your open source contributions to github projects.
- warehouse – still using subversion? Get the best source browser out there.
- xtt – time tracking built for the add & twitter inclined.
- GitNub – OS X GUI for tracking git logs.
22 Comments
Nice work. I’m curious why you’re using different email command syntax from Tender’s “hashtag” syntax?
We went with what we felt was more appropriate for the application. Lighthouse is a little more technical, so having something that matched the syntax we use for searches and bulk edits made sense. We could eventually go in and add hash commands at some point though. That’s not a bad idea.
would love an iphone app. since i am responsible for managing the dev team, i get so many notification emails. an iphone optimized website or app that i can login and manage tickets would be very helpful. thanks!
Nice updates, quite useful. One thing, tho. A while back you changed the tagging functionality such that we can’t see a list of previously used tags under the tag list when editing a ticket unless you start typing a tag. For those users that aren’t in the system every day, remembering the wording of tags is a problem. It was much more “casual-friendly” the old way, where all previously used tags appeared below the tag field and allowed the user to select by clicking.
Any possibility of that feature making a return?
@rob – http://iphone.lighthouseapp.com
Any reason why you can preview things while you’re creating them but not when you’re editing them?
How can we check our current attachment load? We use Lighthouse a lot to track individual documents and spreadsheets, and I’d like to know how close we are to our quota.
+1 for enhancing the tag system to see already used tags.
Greetings, @Zach – The iphone site needs some love; it’s currently not working anywhere near as tightly as it did when they first released it. I have to scroll all over the place to see info. It’s better to go to the real site on the iPhone, but that’s still a someone difficult interface on the small screen.
I’m less about seeing the tags during bug filing (although something like that might be nice), as allowing some kind of tag management for the admin. I have end-users filing bugs, and the tags they come up with are…chaotic. :) I’d love to see all my tags at once and be able to delete, tweak (rename), join, etc., tags without going into every ticket that contains a given tag and fixing it there. I’ve started prefixing ‘my’ tags with an ’@’, so they don’t collide with user tags.
Of course I’m also one of the folks abusing their API for my own projects, so I should put my time where my mouth is and write an external tool to do just that. It’d be a ton of bulk operations, though. Much cheaper to do it on the server-side.
— Morgan
We actually have a Lighthouse app for iPhone available in the store. It’s called Beacon, and gives you full access to your projects, tickets, tags, etc. You can have multiple accounts, and keep track of all your issues. http://itunes.apple.com/us/app/beacon-the-lighthouse-client/id312331775?mt=8
Nice work with the Preview. One thing that I feel can be improved is the adding of a bulleted list. I always have to skip lines between items. Any reason why the LF (line feed) cannot be assumed to mean next entry?
For example:
@List of changes: * Change description 1 * Change description 2@Instead I have to do:
@List of changes:@I really like adding keywords when replying to a ticket. However when I visit the ticket online I noticed that the keywords are still part of the message.
I think that keywords are meant modify the ticket and should be removed from the message body.
Please allow sorting on the priority column. I remember how hard it was to get Lighthouse to even have a priority field and would hate to see it treated like a 2nd class citizen when it comes to sorting. I think everyone agrees that knowing which ticket to tackle next is critical to any ticket management system and sorting will help a lot.
@aubrey—We’re working on integrating preview everywhere, the edit form was overlooked. It will be added soon.
@rishad—Looking at the raw text for your comment, it seems you’re indenting your lists. If there is no indentation, linefeeds work as expected. If there is indentation, then it does seem you need to add another line. This seems to be a problem with our markdown parser, I’ll look into it.
@bastian—We’ve had a few cases where people use keywords unintentionally, and we’d rather preserve the original contents of their messages. I understand the appeal of having them removed from the ticket body, but I doubt we can do this in any way that wouldn’t effect these cases.
@cyrus—I’ll look into it. We don’t have priorities enabled in our own accounts, and it never came up during development or QA of the feature.
At one point it would be nice to have TinyMCE or CKEditor, that would make formatting large amounts of text go a lot faster.
I’d like to second what Cyrus Ghalambor said, I’d like to be able to sort using the Priority column as well.
Just noticed that the delete attachment link is dangerously close to the view link.
Any news on the multi-word tags?
Sanford: Yes, you can use commas to separate tags. We don’t split tags on spaces anymore.
This is only on the web UI… the ticket API did not change how it handles incoming tags.
There’s something wrong with this update. I have added feedback to some bugs and these seem to somehow “merge” with previous entries. So if, for example, I add a comment, and later somebody else changes the status of the bug, I end up with only one comment with the description of the first and the status change and signature of the second.
+1 for enhancing the tag system to see already used tags. Otherwise: great work, keep it coming!
+1 for enhancing the tag system to see already used tags. The new preview and sorting features are nice!
Make your voice heard
Sorry, but comments are closed for this item.