Last modified: 2009-01-30 20:56:29 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 17248 - After replying to a ticket in OTRS, the ticket does not unlock
After replying to a ticket in OTRS, the ticket does not unlock
Status: RESOLVED DUPLICATE of bug 17250
Product: Wikimedia
Classification: Unclassified
OTRS (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Tim Starling
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-30 15:06 UTC by Ryan (Rjd0060)
Modified: 2009-01-30 20:56 UTC (History)
2 users (show)

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


Attachments

Description Ryan (Rjd0060) 2009-01-30 15:06:12 UTC
When replying to a ticket, the ticket should automatically unlock itself after the reply is sent.  It remains locked to the agent who then has to manually unlock it.
Comment 1 Stifle 2009-01-30 18:37:44 UTC
This will be fixed when bug 17250 is, because changing the status dropdown to Closed successfully when you answer a ticket results in the ticket being unlocked as well.
Comment 2 Mike.lifeguard 2009-01-30 20:56:29 UTC
(In reply to comment #1)
> This will be fixed when bug 17250 is, because changing the status dropdown to
> Closed successfully when you answer a ticket results in the ticket being
> unlocked as well.
> 

Duped then

*** This bug has been marked as a duplicate of bug 17250 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links