Bug 310381 - xmlrpc for private bugs
Summary: xmlrpc for private bugs
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: devel
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-28 06:56 UTC by Denise Dumas
Modified: 2013-06-24 02:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-30 23:02:47 UTC
Embargoed:


Attachments (Terms of Use)
example script for xmlrpc runQuery function (795 bytes, text/plain)
2008-03-31 01:51 UTC, Noura El hawary
no flags Details

Description Florian La Roche 2007-09-28 06:56:28 UTC
Description of problem:

Querying all my open bugs via xmlrpc does not include any IT-escalated
private bugs, even if I am fully authenticated to bugzilla.

Can these bugs get enabled for xmlrpc queries?

regards,

Florian La Roche



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Florian La Roche 2007-10-12 06:58:32 UTC
Seems if a real user/password login is used this works ok, but if using
the firefox cookies, then the CanSeeBug() routine in globals.pl is
returning a denied.

regards,

Florian La Roche


Comment 3 Noura El hawary 2008-03-31 01:51:23 UTC
Created attachment 299657 [details]
example script for xmlrpc runQuery function

HI Dennis,

I tried to produce the problem you have reported but couldn't. Using the
attached script i tried to get all your "NEW, ASSIGNED, NEEDINFO, MODIFIED"
bugs and it returned the private IT escalated bugs fine for me for example bug#
145104 . so is this problem still present? if yes please give us an example bug
that you can not access using xmlrpc runQuery.

Comment 4 David Lawrence 2008-11-30 23:02:47 UTC
Please reopen this issue if the problem still persists in the latest Bugzilla version.


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