•  
     
    story #13311 send notification to people using @ notation in trackers
Summary
Empty
send notification to people using @ notation in trackers

I can easily ping people to inform them about "stuff"

Overview

This is not meant to replace the current notification mecanism, that is to say assignement, or "CC fields". This feature is designed to be a one time "ping" of people to inform them about something related to one issue in a follow-up comment (or any text area).

Generally speaking:

  • People should be notified at the time they are mentionned
  • but not after
    • If people should be permanently notified, the regular notification mecanism should be used.
  • If people explicitly set to not be notified on a given artifact (unsubscribe on the artifact or "stop tracker notification") they won't receive an email
    • there is then a "warning feedback" displayed to the user who notified someone that this person won't be notified
  • People receives the notification accordign to their permissions (on project, tracker & fields).
    • If you mention @jdoe in a project she cannot access, she won't be notified.
  • Notification is automatic and not configurable, everytime '@jdoe' string is matched in a supported area (see bellow), jdoe user will be notified.

Note: at XML import there is no notification of people.

Functional

Follow-up comments

At follow-up comment creation (web & REST)

  • When there is a @string mention that match a username, the user is notified
    • if the user should have been notified with another field, there is only 1 notif that is sent
    • it can be used in combination with another notification mecanism. For instance jdoe is notified because assignee only on status changes but somebody mentions @jdoe in ca comment w/o status change => jdoe will get an email for this change.
    • further follow-up comments (without mention of user) won't notify the user

At follow-up comment edition:

  • Same rules apply than at creation. It means that
    • given a first comment with @jdoe (that triggered a notif)
    • whe this comment is updated and that the @jdoe string is still in the comment
    • then a mail is sent to jdoe
  • => Side Effect if @jdoe was not an actual user when the comment was created but is created later on, when the initial comment is update, @jdoe gets the notification.

Textarea fields

At text creation (web & REST):

  • (creation means from an Empty text to something not empty
  • When there is a @string mention that match a username, the user is notified
    • if the user should have been notified with another field, there is only 1 notif that is sent

At text update (web & REST)

  • Same rules apply than at "creation"

User is notified Only when the text field she is mentionned in is updated. Another way of saying it is that if @jdoe is mentionned in bug description, he won't be notified when "status" or "title" are changed or when a follow-up comment is added. How ever, as long as the string '@jdoe' is present in bug description, everytime description get changed, @jdoe will be notified.

String fields

Question: As of today, @mention is not supported in those fields ?

Empty
Laurent CHARLES (lcharles)
Status
Empty
Ready (stalled)
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#13311
Manuel Vacelet (vaceletm)
2019-04-29 18:51
2019-04-24 13:26
4040

References
Referencing story #13311

Artifact Tracker v5

epic #2047 Tracker

Follow-ups

User avatar

It looks good and pretty complete. Thx.

  • The first need is for follow-up comments and one-time notifications. It fulfills the need.
  • I am not sure it is useful for other fields (text, string, etc.). I even wonder if it would not be a wrong behaviour.
    • If I write @machin in a text, it may more to illustrate my text than notify the user (ex: Bug description "When I write @machin I have an error").
    • If I need to notify Machin I assigne or cc explicitely.
  • Is-it more simple to ignore it for art fields?
  • We may consider to cc the automatically... not sure it is a good idea.

  • Category set to
User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • CC list set to Laurent CHARLES (lcharles)