How to use history for comments notification?

Follow

Comments

8 comments

  • Avatar
    Michael Decleene

    +1 to wanting this. 

  • Avatar
    Nathan Davis

    At this point, it appears to me that the only way to do this currently in Mingle is to write a separate program that uses the Mingle API to periodically pull from the history, and then programmatically interrogate each revision to see if there are comments, then send out emails programmatically based on the results of the interrogation.  If anybody knows differently, please let me know.

  • Avatar
    Suzie Prince

    Hi all


    We do not have the ability to do this build into Mingle but we do have a story for this in our backlog as this has been requested for before.


    We will update you if we add this feature.


    Thanks for the feedback. Suzie

  • Avatar
    mattgow

    You can kinda sorta simulate this by setting up a transition called something like "add comment" which requires a comment and sets some (otherwise meaningless) card property E.g. setting a property called "Comments" to "comment added". You then get people to subscribe to changes to the "Comments" card property and try to convince everyone to use your "add comment" transition rather than typing directly into the comment box on the right.

  • Avatar
    Matt Quagliana

    Hmmm... interesting idea. How does the "comment added" property get reset? The history filter looks for a state changes so "comment added" must get reset at some point or you will only be notified of the first comment.

  • Avatar
    Matt Quagliana

    One workaround is to subscribe to notifications via email and then let your email client filter the messages based on content. When a user adds a comment the email includes the text "Comment added:". You could write a mail filter that colors those messages, places them in a special folder, etc.


    --


    Matt

  • Avatar
    mattgow

    Good point.


    Perhaps you could set a date property like "commented on" and have it set to (today)... though I wonder if that would effectively mean getting only one comment each day. Another property like "commented by" getting set to (current user) could similarly help though perhaps only if a different person comments each time.


    I confess that I shared the suggestion without having tested it... what we have ended up doing (aside from requesting the same feature you want) is what Matt Quagliana suggests in the next comment... subscribing to everything and just dealing with the SPAM.


    We are also looking into rolling our own notifications stuff via the API but gee I'd prefer not to! Has anyone got a working example of something along those lines?

  • Avatar
    mattgow

    Looking for a cheap way to get this going (i.e. cheaper than writing an app to poll via the API) I'm toying with the idea of using a content filter in Postfix to monkey patch things. E.g.



    1. Create a property called "cc-me" on cards and ask people to put their email addresses in it (comma separated) if they want to be on the comments-only mailing list for that card.

    2. Create a dummy user in Mingle that is subscribed to everything (waste of a license... but...)

    3. Set up a filter in postfix (on the Mingle machine) that looks for messages addressed to the dummy user with "Comment added" in the body and have it grab any addresses from the "cc-me" propery in the body of those message and inject them into the "bcc" field before delivering the message.


    As I write this it sounds very ugly and people who had an existing subscription that overlaped with the card would sometimes get two emails. But it might work.


    An advantage is that it allows people who are not on the team to get emails regarding a bug or feature if someone adds their address to the "cc-me" property.


    Counter suggestions anyone?

Please sign in to leave a comment.