Last modified: 2013-07-07 10:28:35 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 T52866, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 50866 - Make RT more transparent
Make RT more transparent
Status: RESOLVED DUPLICATE of bug 30413
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-06 15:13 UTC by Carl Fürstenberg
Modified: 2013-07-07 10:28 UTC (History)
1 user (show)

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


Attachments

Description Carl Fürstenberg 2013-07-06 15:13:06 UTC
Currently you need to be a approved member to read any RT ticket. While I can understand that some tickets might need some secrecy, currently it's impossible for "normal people" to read tickets, or even find if a request has ever been made (well, not doing the full NSA though).

I think any ticket that hasn't been marked as secret, should be publicly traceable without the need for a login to access the information.
Comment 1 Sam Reed (reedy) 2013-07-07 02:36:04 UTC
Marking tickets as "secret" is a bit daft way of doing it. It could be done more like how security bugs are handled in bugzilla.

Things like vendor contact and procurement can then be kept with similar segregation in their appropriate queues as they have now from non ops and appropriate staff,
Comment 2 Andre Klapper 2013-07-07 10:28:35 UTC
(In reply to comment #0)
> Currently you need to be a approved member to read any RT ticket.

Anybody who has access to a specific RT ticket can CC your email address on that ticket - it's more that you yourself cannot actively access any tickets without that.

This sounds like a duplicate of bug 30413 to me, hence marking as dup. And that's ops territory to discuss. :)

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

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


Navigation
Links