headers
Volkmar Schau | 11 Sep 2005 14:29
Picon
Favicon

Create new queue

Greetings,

I'm using horde 3.0.5 (php 4.3, mysql 4.0) with nightly snapshots of 
whups. Installation and configuration works fine, no problem.

If I create a new queue edit settings, I get lots of messages. Created 
queue isn't useable. What's wrong, I have no idea?

Best regards,
Volkmar Schau

Step 1
------
I add a new queue (queue name und description) I get a lot of notice 
infos like:

Notice: Undefined index: name in 
/var/home/web/horde3/whups/lib/Admin.php on line 148

Notice: Undefined index: readonly in 
/var/home/web/horde3/whups/lib/Admin.php on line 152

Notice: Undefined index: name in 
/var/home/web/horde3/whups/lib/Admin.php on line 153

Notice: Undefined index: readonly in 
/var/home/web/horde3/whups/lib/Admin.php on line 155

Notice: Undefined index: description in 
/var/home/web/horde3/whups/lib/Admin.php on line 156
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin Lohmeier | 11 Sep 2005 15:23
Picon

Re: Create new queue


Volkmar Schau wrote:
> Greetings,
> 
> I'm using horde 3.0.5 (php 4.3, mysql 4.0) with nightly snapshots of 
> whups. Installation and configuration works fine, no problem.
> 
> If I create a new queue edit settings, I get lots of messages. Created 
> queue isn't useable. What's wrong, I have no idea?
> 
> Best regards,
> Volkmar Schau

Hi,

get whups from cvs. This problem has been fixed a few days ago.

bye, Martin

--

Powered by Mac OS X
Permalink | Reply | 0 comments |
headers
Andrew Preece | 20 Sep 2005 23:28

access Whups API through SOAP

I'm trying to access the Whups API from c# in visual studio, and I was
hoping someone here could help me. 

My current code is:

			com.canfer.www.hordeService ws = new
cmdhorde.com.canfer.www.hordeService();
			ws.Credentials = new
System.Net.NetworkCredential("user","password");
			ws.PreAuthenticate = true;
			
			string[] str = ws.hordelistAPIs();
			foreach (string item in str)
				Console.WriteLine(item);

However, I an error that says
method '{urn:horde}hordelistAPIs' not defined in service

I get the same error, no matter which API I try to call. 

Any help would be greatly appreciated. 

Thanks, 
Andrew. 

--

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: whups-unsubscribe <at> lists.horde.org
(Continue reading)

Permalink | Reply | 1 comment |
headers
Chuck Hagenbuch | 21 Sep 2005 05:59
Favicon
Gravatar

Re: access Whups API through SOAP

Quoting Andrew Preece <andrew.preece <at> canfer.com>:

> However, I an error that says
> method '{urn:horde}hordelistAPIs' not defined in service

You need to either call "horde.listAPIs" or "horde/listAPIs" - you need 
some form of the seperator. I don't know how to do that specifically in 
c#.

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams
--

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: whups-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Paul Hancock | 21 Sep 2005 16:26
Picon
Favicon

Whups permissions

Is there any sort of guide or documentation for whups
permissions?  I looked around, but didn't find anything.

Specifically:

What does permissions set at the 'Tickets (whups)' level
control?

What does permissions set at the 'Queues (queues)' level
control?

What is the difference between 'Show' and 'Read'?

Thanks for any help you provide.

		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
--

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: whups-unsubscribe <at> lists.horde.org
Permalink | Reply | 0 comments |
headers
Paul Hancock | 21 Sep 2005 16:43
Picon
Favicon

Setup question

I have whups set up, and have been using it for a few months. 
It's been great so far -- quite a nifty bug tracker!

My current setup has one queue for new tickets, and it allows
guest to post to it. Other queues are set up, but they are only
viewable by designated groups.  I don't want guest to be able to
view the tickets, since there may be sensitive or abusable
information in them.

The concept was that someone could post a ticket in the new
tickets area.  Any representative (including non-admin) could
then move the ticket to the proper queue for further attention. 
At the time I set this up, non-administrators could move
tickets, which was ideal, since I did not want
non-administrators having the ability to change the whups
settings, only to move tickets around.  Unfortunately, Set Queue
is now an administrator-only function.  

Are there any suggestions on how I can accomplish the same thing
that I've outlined above with the current code?  If it were
possible to set visibility on a ticket by ticket basis, an
authorized representative could limit visibility to only the
sensitive tickets.  I did not see a way to do that, though.

My concern is that if I'm the only one able to move tickets from
the new ticket queue, I'm the bottleneck, and the ticket is
sitting there visible for all to see, even if it has info I
don't want the world to see.

Thanks for any suggestions you have!
(Continue reading)

Permalink | Reply | 8 comments |
headers
Chuck Hagenbuch | 21 Sep 2005 20:17
Favicon
Gravatar

Re: Setup question

Quoting Paul Hancock <paulh1221 <at> yahoo.com>:

> The concept was that someone could post a ticket in the new
> tickets area.  Any representative (including non-admin) could
> then move the ticket to the proper queue for further attention.
> At the time I set this up, non-administrators could move
> tickets, which was ideal, since I did not want
> non-administrators having the ability to change the whups
> settings, only to move tickets around.  Unfortunately, Set Queue
> is now an administrator-only function.

Not that this helps you, but Set Queue has never _intentionally_ been 
available to non-admins. :)

> Are there any suggestions on how I can accomplish the same thing
> that I've outlined above with the current code?  If it were
> possible to set visibility on a ticket by ticket basis, an
> authorized representative could limit visibility to only the
> sensitive tickets.  I did not see a way to do that, though.

No, permissions are queue-based, not individual ticket-based.

What would people think of allowing users to move tickets between any 
queues that they have write access to? Set Queue was admin-only in the 
past because it can mean changing the type of a ticket as well, but the 
UI walks you through all necessary changes and makes sure the ticket is 
still valid in the new queue, so I don't think that's a concern.

-chuck
(Continue reading)

Permalink | Reply | 7 comments |
headers
Jan Schneider | 21 Sep 2005 23:25
Favicon
Gravatar

Re: Setup question

Zitat von Chuck Hagenbuch <chuck <at> horde.org>:

> What would people think of allowing users to move tickets between any
> queues that they have write access to? Set Queue was admin-only in the
> past because it can mean changing the type of a ticket as well, but the
> UI walks you through all necessary changes and makes sure the ticket is
> still valid in the new queue, so I don't think that's a concern.

That would mean that guest could also change queues, right? I 
personally don't think it's a problem, I just want to make it clear. 
Fine by me.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/

--

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: whups-unsubscribe <at> lists.horde.org
Permalink | Reply | 3 comments |
headers
Kevin M. Myer | 21 Sep 2005 23:54

Re: Setup question

Quoting Jan Schneider <jan <at> horde.org>:

> Zitat von Chuck Hagenbuch <chuck <at> horde.org>:
>
>> What would people think of allowing users to move tickets between any
>> queues that they have write access to? Set Queue was admin-only in the
>> past because it can mean changing the type of a ticket as well, but the
>> UI walks you through all necessary changes and makes sure the ticket is
>> still valid in the new queue, so I don't think that's a concern.
>
> That would mean that guest could also change queues, right? I
> personally don't think it's a problem, I just want to make it clear.
> Fine by me.

Until you have some joker go through and change the queues on all the tickets
that are guest-readable..  Having it be configurable to give guests that
privilege would be ok (because maybe some admin wants that to happen), but
essentially, allowing a guest to move a ticket to any visible queues shouldn't
be a default privilege.  That should be a default admin or technician 
function,
only, at least here it is (but with a different ticket system).  How annoying
would it be if I requeued all the bugs.horde.org tickets in other 
queues? Presumably I have write access to all the modules/queues there 
(since I can
create a ticket in any of them), so this change would allow me to do 
that, no? But I might not understand your proposal either.. (but then 
again, I think
relying on unauthenticated guest access, with an easily spoofed email key can
be problematic too :)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rodion Serebryakov | 22 Sep 2005 00:35

Re: Setup question

Chuck Hagenbuch wrote:

> What would people think of allowing users to move tickets between any 
> queues that they have write access to? Set Queue was admin-only in the 
> past because it can mean changing the type of a ticket as well, but the 
> UI walks you through all necessary changes and makes sure the ticket is 
> still valid in the new queue, so I don't think that's a concern.

I think, this would be very useful.

I get requests to move tickets from one queue to another often enough to
wish for owners' ability to do it on their own.
Some of the times the need to move tickets is there because of the
requester's lack of understanding of which queue suits the problem best,
and other times it's because the ticket evolves to a whole different
animal over time.

Sometimes I have to change the requester, too (micro-surgery on the
database).  Maybe, that is something that admin should be allowed to do?

Rodion
--

-- 
Whups mailing list - Join the hunt: http://horde.org/bounties/#whups
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: whups-unsubscribe <at> lists.horde.org
Permalink | Reply | 2 comments |

Gmane