action #2564
closed
Implement proper notifications through OBS comments
Added by ancorgs almost 10 years ago.
Updated almost 10 years ago.
Description
Now that #2424 is done and we have a prototype able to write and 'remember' comments. We need to implement the comments in a way that makes sense (not spamming) and is useful for users involved in staging projects.
Files
hmm...to be honest, I haven't better idea how to "don't spamming", even put all @users in the first comment, they'll still receive the mail once have the other requests add to the same group later, I can't figure out a nice idea...
yes, but in general I dislike getting more mails than the number of commands were called. E.g. accept should send one mail, and select should send one mail - if you call select multiple times at different time of day, then be it.
attached my hand-draw idea. have been discuss about it on FT
So everyone gets one mail with the new summary everytime something changes? I kind of like that.
But I would replace "rq_id xxx @creator" with "Package aaa submitted by @creator" :)
oops, redmine rendered my markdown - I meant to have it verbatim in the task :)
- Status changed from New to In Progress
- Assignee changed from mlin7442 to ancorgs
- % Done changed from 0 to 70
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
Also available in: Atom
PDF