User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:184.108.40.206) Gecko/20070725 Firefox/220.127.116.11 Build Identifier: 3.0.1 In the current whining category, you simply whine to a user or a group. But let's imagine I want to whine at the assignee of a critical bug when it has not been updated during one week! Reproducible: Always Steps to Reproduce: 1. Look at whining settings. Actual Results: Currently the only way to do this is to create one search and one whine event by person which may be assignable. And even here you may miss some case if you forget someone, and you always have to update this when people are going in and out of the company, and so on. This is not maintenable. Expected Results: I would like a system where you can send a whine to a field specific to a bug. In this case, you will have one single search looking for all critical bugs unmodified in a week, whoever they belong to. And you create one single whining event with "Mail to" "field" for instance, and there you can add a field (for instance the "Assigned To" field). Of course this requiere the field to be a valid user.
I have added a comment in BUG287328 which is related. This is not exactly the same thing, so maybe should I start another enhancement ticket, but here I think that having a field which can have a type "user", then you may link it from the whining system as a recipient field. In my case this is important because I propose this enhancement because I would like to be able to whine at customers, not at assignees. I would create a "customer" field (these ones having only restricted access), and if they don't provide the requested information after some time, I would notify them automatically that the ticket will be closed after some time if they don't provide the needed information for their problems.
I thought this request was already filed, but I cannot find it. I agree it would be cool to be able to use %reporter% and %assignee% as username.
(In reply to Frédéric Buclin from comment #2) > I thought this request was already filed, but I cannot find it. Bug 300799?
The duplicate includes also "%%defaultasignee%% for the component.