Flyspray - The bug killer!

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category Backend/Core
  • Assigned To No-one
  • Operating System Linux
  • Severity Medium
  • Priority Very Low
  • Reported Version 1.0 devel (github master)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Thanatermesis - 26.10.2017

FS#2447 - Allow notifications when a new task is created

The only (only!) feature that I have missing in Flyspray is an option to receive email notifications when a new task is created

I think that this could be in the profile of the user, and/or in the main configurations as “send a notification to the -group- (admins?) when a new task is created”

Thanks a lot! flyspray r00lz after all these years, never failed, no bugs, no hacks, fast and efficient! :)

A Happy user.

Project Manager
peterdd commented on 28.10.2017 22:58

What is your user role in your flyspray install? If you are the only project manager, you can set your email address in the project settings and set the events you want receive, also the 'new task' event is there, see screenshot.

Another workaround could be setting an email address there that forwards them to a list of your team mates like mailing list.

About the feature requests:

As user profile settings: would require a new setting on a per project level in conjunction with user's permissions.
As group permission: maybe with notification channels (email, jabber/xmpp, ..) the user prefers.

Must definitely done decoupled from the http request of the user who creates the new task. (using the notification/scheduler)

Maybe this feature can be implemented when reviewing the notification stuff, e.g. by giving more control how when notifications are send to a user and when not. (like settings per multiple email addresses per user, avoid spamming the user on high activity projects like giving them the possibility to receive a daily notification of lets say 15 changes instead of receiving 15 email notifications, or grouping the "quickedit" task changes together for a period of time ..)

examples of permissions to check:

  1. Has the user view tasks permission in that project of that new task? If user only can see parts of tasks (like only the summary), then only send the allowed parts in the notification.
  2. When the task has the 'private' check, then also send them only to users who are allowed to receive them (like project managers)
Thanatermesis commented on 29.10.2017 13:04

Hum... by some reason I always thought that these were the settings of the email configuration (like the profile for this project when sending emails, like "users should receive email notifications with these settings and when...)

Maybe the "email address" should (if not does it yet) accept multiple emails, so like a list of emails (newline or comma-separated) that will receive notifications (so like admins of the project)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing