Last modified: 2009-02-19 17:06:34 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T19569, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 17569 - Getting follow-up notifications for tickets that we don't own
Getting follow-up notifications for tickets that we don't own
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
OTRS (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-02-19 15:53 UTC by Ryan (Rjd0060)
Modified: 2009-02-19 17:06 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ryan (Rjd0060) 2009-02-19 15:53:05 UTC 
We should only get follow up notification emails for replies that come in to tickets that we own, however, we're getting them for others (tickets that we've not even touched).  See https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketHistory&TicketID=2483572 for example.
Comment 1 Tim Starling 2009-02-19 16:01:29 UTC 
Isn't this just a duplicate of bug 8662?
Comment 2 Ryan (Rjd0060) 2009-02-19 16:11:24 UTC 
(In reply to comment #1)
> Isn't this just a duplicate of bug 8662?
> 

I don't know if it is or not, as I don't know if it is going to "all queue agents" as 8662 says.
Comment 3 Guillaume Paumier 2009-02-19 17:06:34 UTC 
This specific queue (info-en::Copyvio) was configured so that "Ticket lock after a follow up:" was disabled, so it makes sense that the system send a notification to all volunteers who have this queue in "My queues". The option is enabled now, so it should be fixed. Please re-open if not.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links