tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/2065-the-new-email-notification-formatLighthouse: Discussion 2014-10-28T00:19:25Ztag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-08T11:39:12Z2013-10-08T11:39:12ZThe new email notification format<div><p>Hi, thx for a great system. We've noticed the latest updates to
the email notification format, which we do appreciate. However, the
quoting of new text is really confusing - was that deliberate? We
would expect new text to be unqouted and quoted text to be
quoted.</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-08T20:40:33Z2013-10-08T20:40:33ZThe new email notification format<div><p>Hey Nils,</p>
<p>I think it was intentional for some reason that I can't
remember, but I'll take another look at it later this week (I'm
kinda full today). Do you have any other comments about it, things
you'd like improved?</p>
<p>Thanks!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-09T17:08:00Z2013-10-11T00:36:41ZThe new email notification format<div><p>Hi, thx for quick response, no other feedback besides: good
job!</p>
<p>Best<br>
/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-11T00:40:20Z2013-10-11T00:40:20ZThe new email notification format<div><p>Hey Nils,</p>
<p>I took another look at the email, and I think I added that
blockquote to improve readability and clearly delineate the reply
from the rest of the email, which already has a lot of stuff. It's
not semantically correct but I find it easier to read. Plus
blockquotes within that one still show up properly, so it doesn't
feel like a big problem.</p>
<p>What do you think? Has it been a big problem for you? Do you
have specific ticket notifications I could look at to get a better
feel of how we can improve this?</p>
<p>Thanks!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-28T17:02:13Z2013-10-28T17:02:13ZThe new email notification format<div><p>Hey Nils,</p>
<p>Just following up on this to see if you needed help with
anything else.</p>
<p>Thanks!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-29T10:11:01Z2013-10-30T19:07:43ZThe new email notification format<div><p>Julien,</p>
<p>Thx for following up. The blockquote does not impose any
problems for us, it was just an observation. We’ve gotten
used to it now! Your reasoning behind it makes sense, and it does
single out the actual reply from the general ticket metadata.</p>
<p>Another thing we’ve been discussing: after your
notification refactoring, we also get notifications on ticket
edits, which is good. However, we do see a lot of
“unnecessary” notifications of edits made within a
short period of time, e.g. format and spelling corrections etc. So
sometimes we get spammed. How about implementing a grace period of
e.g. 1 minute after a create or edit operation has been made before
you send the notification? And reset the grace period if the user
edits the same post within the minute? Attaching an example where
one of our customers edited the same post multiple times (I think
he was trying to get the formatting right). This resulted in five
emails sent to a lot of people, where the actual content was the
same.</p>
<p>Keep up the good work!</p>
<p>Best<br>
/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-30T19:10:16Z2013-10-30T19:10:16ZThe new email notification format<div><p>Hey Nils,</p>
<p>Sorry I didn't get back to you earlier. This seems like a good
idea. I've been quite busy lately, so I'm not sure when I'll have
time to implement it, but I'll keep it in my queue for when things
lighten up a bit.</p>
<p>Thanks for all the feedback.</p>
<p>Cheers!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-31T13:21:35Z2013-10-31T18:26:01ZThe new email notification format<div><p>Julien,</p>
<p>Thx for the update, guessing it’s a nice-to-have
anyway.</p>
<p>Another thing that I have been wanting to ask you, but never
gotten around to, is to request the ability to create custom
dropdowns for tickets per project. Currently, there are four ticket
dropdowns (Responsible, Milestone, State and Importance). And on
top of this, tags can be used to provide a ticket with whatever
information. However, we see the need for a more “controlled
manner” than tags in order to get input from our customers,
i.e. I want to control the possible options. As an example I would
want to have a dropdown for “originating version” where
the customer should select the software version (from a controlled
list) in which the issue has been found. Today we are using the
Milestone feature for this, and it gets really confusing as we also
use the Milestone to indicate to the customer when it will be fixed
(see example here: <a href=
"https://vidispine.lighthouseapp.com/projects/66815-cantemo/tickets/371-shape-metadata-is-not-serachable#ticket-371-2">
https://vidispine.lighthouseapp.com/projects/66815-cantemo/tickets/...</a>)</p>
<p>For another customer (partner really), we are currently using
the Milestones feature to indicate in which of their customer
systems an issue has occurred – this should really be entered
in a different way, but I’m not able to get them to use the
tags function reliably or consistently.</p>
<p>Do you understand the request?</p>
<p>/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-10-31T18:35:24Z2013-10-31T18:35:24ZThe new email notification format<div><p>Hey Nils,</p>
<p>Totally understand. We have always been against custom fields
for Lighthouse, as we don't want to turn into one of those horrible
enterprise bugtracker that make you want to hurt yourself. We want
to keep Lighthouse simple, but there is definitely a need there,
that tags, because they are freeform and unrestricted, do not quite
address.</p>
<p>The solution we have for this would be to implement "labels",
kinda like Github does it, with colors and stuff. Unfortunately,
this is scheduled to be part of a rewrite of Lighthouse we have
started, and so not due for a couple of months (though we strive to
keep Lighthouse simple, the codebase itself is quite large).</p>
<p>So yes to the feature, but in the future.</p>
<p>Cheers.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-01T12:46:14Z2013-11-04T22:36:58ZThe new email notification format<div><p>Sounds great, keep up the good work.</p>
<p>Another request (guess you regret opening the Swedish vault of
requests now.. ☺) would be to expose ticket tags in the
/Tickets-view in a project. Example: in this customer project
(<a href=
"https://vidispine.lighthouseapp.com/projects/56451-hogarth/tickets">https://vidispine.lighthouseapp.com/projects/56451-hogarth/tickets</a>)
we are using tags to indicate to our customers in which release we
aim to fix the issue. But in the tickets-view the tag info is not
displayed, so one has to open every ticket to see the details. How
about exposing the tags in a separate column, or as part of the
mouse-over-tooltip?</p>
<p>/nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-04T22:42:41Z2013-11-04T22:42:41ZThe new email notification format<div><p>Hey Nils,</p>
<p>I'm afraid it's probably another thing we'll address in the
rewrite.</p>
<p>Can you tell me more about the use case though? You could maybe
use a bin with a tag search to address this particular issue, or a
sort by milestone.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-05T10:34:28Z2013-11-05T21:44:41ZThe new email notification format<div><p>We’ve already “spent” the milestone feature to
indicate origin and target release for the fix, for this partner.
The partner adds tags to the ticket to indicate which end customer
it comes from, if it is live or staging, severity according to them
etc etc. Seeing this at first glance in the ticket view (as
mouse-over information) is very very valueable to both them and
me.</p>
<p>Likewise, if you implement support for custom dropdowns (same
style as Milestone), this information would also be good to display
in the default ticket view somehow, as a column or as mouse-over
tooltip.</p>
<p>/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-05T21:49:49Z2013-11-05T21:49:49ZThe new email notification format<div><p>Hey Nils,</p>
<p>Thanks for the additional information. It is unlikely that we
will develop those features for the current version of Lighthouse,
as this is the kind of feature that requires some thoughts in terms
of UI and UX, and that we can't just pile on top of the existing
ticket list view. I would rather spend that time doing it right in
the new UI, where we will have more control and freedom.</p>
<p>Let me know if you have any question.</p>
<p>Cheers!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-26T20:19:07Z2013-11-26T20:19:07ZThe new email notification format<div><p>Follow up on this discussion, since it's public and it might
help other users. I'm not sure when we'll implement a good solution
to show tags on the ticket list, so here is a hack to get it
now.</p>
<p>If you use Chrome, install <a href=
"https://chrome.google.com/webstore/detail/tampermonkey/dhdgffkkebhmkfjojejmpbldmpobfkfo">
Tampermonkey</a>, if you use Firefox, install <a href=
"https://addons.mozilla.org/en-US/firefox/addon/greasemonkey/">Greasemonkey</a>,
and then install <a href=
"http://userscripts.org/scripts/show/184669">this script</a>. You
can look at <a href=
"http://userscripts.org/scripts/review/184669">the source</a>, it's
very straightforward.</p>
<p>Cheers.</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-26T20:27:04Z2013-11-26T20:28:46ZThe new email notification format<div><p>Works like a charm!!!!</p>
<p>Tried the Chrome part. 1 minute install, smooth like a glove,
fabulous!!</p>
<p>/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872013-11-26T20:30:09Z2013-11-26T20:30:09ZThe new email notification format<div><p>Hey Nils,</p>
<p>Great :)</p>
<p>Cheers!</p></div>Julientag:help.lighthouseapp.com,2008-09-20:Comment/292663872014-03-14T09:05:24Z2014-03-14T09:05:24ZThe new email notification format<div><p>Hi, wanted to understand your progress of your Lighthouse
rewrite you refer to in post 9 above. We would really, really,
really like some more flexibility in adding metadata to the tickets
(custom dropdowns). I spend most my day in Lighthouse and this hits
me every hour.</p>
<p>Best<br>
/Nils</p></div>Nils Lefringtag:help.lighthouseapp.com,2008-09-20:Comment/292663872014-03-14T14:41:15Z2014-03-14T14:41:15ZThe new email notification format<div><p>Nils -</p>
<p>The rewrite/redesign is still a work in progress. We've got
tickets associated with this discussion and when we have them
scheduled for a development cycle we'll update you.</p>
<p>Thanks for your patience,<br>
Nicole</p></div>Nicoletag:help.lighthouseapp.com,2008-09-20:Comment/292663872014-03-14T19:20:51Z2014-03-14T19:20:51ZThe new email notification format<div><p>Ok, thank you. And sorry for shooting multiple feature requests
at you in one thread! I yell at our customers when they do that.
:)</p></div>Nils Lefring