#2502 Mass edit should send summary emails

asf_release_1.0.0
closed
nobody
Tracker
Cory Johns
2013-04-22
2011-07-21
Mark Ramm
No

Related

Tickets: #2502
Tickets: #5081
Tickets: #5656
Tickets: #6203

Discussion

  • Dave Brondsema
    Dave Brondsema
    2012-09-05

    Where would we send the summary to? If people are subscribed to individual tickets, they still should be notified.

     
  • Dave Brondsema
    Dave Brondsema
    2012-11-16

    • summary: Mass edit should log something in comments and send one summary email --> Mass edit should send one summary email
     
  • Dave Brondsema
    Dave Brondsema
    2012-11-16

    A changelog comment is added to each ticket which sends out a notification. We need to bypass that and instead roll up all the changes into one email per person who is subscribed to one of the ticket(s). Each email will have to be filtered to show just the tickets that user is subscribed to (and has permission to view).

     
  • Dave Brondsema
    Dave Brondsema
    2012-11-16

    • summary: Mass edit should send one summary email --> Mass edit should send summary emails
     

  • Chris Tsai
    2013-01-22

    • labels: --> support, p3
     

  • Anonymous
    2013-03-03

    Originally by: wohler

    The idea is that if you affect 100 tickets, you don't want to generate 100 emails. Just one. I'd imagine that you would build a set of addresses in the affected emails and send a single email with a summary of the bulk change.

    We don't want the email to be huge, so please do not include more than one line per affected ticket. Number and summary is probably enough.

     

  • Anonymous
    2013-03-03

    Originally by: earnie

    Didn't you read Dave's comment at d933? This ticket is more about how to send one email to people who are subscribed to an individual ticket being changed. If the person is subscribed to just one ticket then that person will only see the change to that one ticket. If he is subscribed to two of the tickets then he will receive one email about the two tickets. It will be similar to a digest mode for a mail list but in this case the list is each individual user so there are multiple lists to care for.

    As an admin you will see 100 changes in that one email because you would be subscribed to all 100 of the tickets. Perhaps the format of the email should change if an individual receiving an email receives more than five of the changed tickets. Maybe if an individual is receiving an email containing all of the changes should receive a link to a log of the changed tickets. Maybe a log display should be created for each individual user for the changed subscribed items with a link to the comment of the change. Then allow the user to opt-out of the email notification and they can monitor the log subscriptions via RSS or just by clicking a link from their account subscriptions.

     

  • Anonymous
    2013-03-03

    Originally by: wohler

    Somehow I missed that :-). The behavior you both describe is what I'd expect. Thanks!

     
    • labels: support, p3 --> support, p3, 42cc
    • status: open --> in-progress
     
  • Created #300: [#2502] Mass (bulk) edit should send summary emails (3cp)

     

    Related

    Tickets: #2502

  • Dave Brondsema
    Dave Brondsema
    2013-03-22

    We'd also need to send a notification to the email address specified in the tool-wide settings (if set).

     
  • Should we include a changelog for every ticket in a summary report? If so, report may be pretty long.

    I see a couple of options here:

    (1) Include only list of affected tickets and, maybe, new values for fields. For example:

    - status: unread
    - milestone: 2.0
    
    Affected tickets:
    
    - [bugs:#1] first
    - [bugs:#2] second
    - ...
    

    (2) Group tickets by change sets, then report would look something like this:

    - status: open -> unread
    - milestone: 1.0 -> 2.0
    
    Affected tickets:
    
    - [bugs:#1] first
    - [bugs:#2] second
    
    - status: accepted -> unread
    
    Affected tickets:
    
    - [bugs:#3] third
    

    and so on.

    (1) seems easier to implement, and it produces a more concise report.

    (2) is harder, but more precise in what has been actually changed.

     

  • Anonymous
    2013-04-11

    Originally by: earnie

    I would prefer something like:

    Mass edit changing:
    status: open
    milestone: 2.0
    
    ticket: [bugs:#1]
    status: unread -> open
    milestone: 1.0 -> 2.0
    
    ticket: [bugs:#2]
    status: pending -> open
    milestone: 2.0 -> 2.0
    
     
  • Dave Brondsema
    Dave Brondsema
    2013-04-11

    I think seeing the previous value is important, so I'd rather not have Igor's suggestion #1. If multiple fields are being changed, I think Earnie's suggestion makes the most sense since it is organized by ticket rather than grouped by field. It might be a bit verbose but I don't think that's really a problem since it'll be tons better than lots of separate emails like we currently have :)

     
    • status: in-progress --> code-review
     
  • Closed #300. je/42cc_2502

     
  • Cory Johns
    Cory Johns
    2013-04-22

    • QA: Cory Johns
     
  • Cory Johns
    Cory Johns
    2013-04-22

    • status: code-review --> closed
    • Milestone: forge-backlog --> forge-may-03