[horde] whups, ticket type is already selected with default, why?

[ANANT S ATHAVALE]

----- Message from ANANT S ATHAVALE <asa at isac.gov.in> ---------
    Date: Wed, 13 May 2015 10:32:54 +0530
    From: ANANT S ATHAVALE <asa at isac.gov.in>
Subject: Re: [horde] whups, ticket type is already selected with default, why?
      To: horde at lists.horde.org


> ----- Message from Michael J Rubinsky <mrubinsk at horde.org> ---------
>      Date: Tue, 12 May 2015 14:14:30 -0400
>      From: Michael J Rubinsky <mrubinsk at horde.org>
> Reply-To: mrubinsk at horde.org
>   Subject: Re: [horde] whups, ticket type is already selected with  
> default, why?
>        To: horde at lists.horde.org
>
>
>> Quoting ANANT S ATHAVALE <asa at isac.gov.in>:
>>
>>> ----- Message from Michael J Rubinsky <mrubinsk at horde.org> ---------
>>>  Date: Tue, 12 May 2015 00:45:36 -0400
>>>  From: Michael J Rubinsky <mrubinsk at horde.org>
>>> Reply-To: mrubinsk at horde.org
>>> Subject: Re: [horde] whups, ticket type is already selected with  
>>> default, why?
>>>    To: horde at lists.horde.org
>>>
>>>
>>>> Quoting ANANT S ATHAVALE <asa at isac.gov.in>:
>>>>
>>>>> ----- Message from Michael J Rubinsky <mrubinsk at horde.org> ---------
>>>>> Date: Mon, 11 May 2015 09:34:43 -0400
>>>>> From: Michael J Rubinsky <mrubinsk at horde.org>
>>>>> Reply-To: mrubinsk at horde.org
>>>>> Subject: Re: [horde] whups, ticket type is already selected with  
>>>>> default, why?
>>>>>  To: horde at lists.horde.org
>>>>>
>>>>>
>>>>>> Quoting ANANT S ATHAVALE <asa at isac.gov.in>:
>>>>>>
>>>>>>> Dear List,
>>>>>>>
>>>>>>> Under what circumstances, Ticket type is not selectable? PFA image.
>>>>>>>
>>>>>>
>>>>>> This screenshot looks like it's *after* the ticket type was  
>>>>>> already selected.
>>>>>>
>>>>>> -- 
>>>>>> mike
>>>>>> The Horde Project
>>>>>> http://www.horde.org
>>>>>> https://www.facebook.com/hordeproject
>>>>>> https://www.twitter.com/hordeproject
>>>>>
>>>>>
>>>>> ----- End message from Michael J Rubinsky <mrubinsk at horde.org> -----
>>>>>
>>>>> No. This is the screen which I get as soon as I click on New  
>>>>> Ticket.  That's what makes me wonder, what configuration would  
>>>>> have made it.
>>>>
>>>> Then you either only have a single ticket type configured for  
>>>> that queue, or the user creating the ticket does not have  
>>>> permissions to change to another type.
>>>>
>>>> -- 
>>>> mike
>>>> The Horde Project
>>>> http://www.horde.org
>>>> https://www.facebook.com/hordeproject
>>>> https://www.twitter.com/hordeproject
>>>
>>>
>>> ----- End message from Michael J Rubinsky <mrubinsk at horde.org> -----
>>>
>>> I have given Read, Write and Edit permissions for all  
>>> authenticated users and Update to only one individual user.  And I  
>>> am trying to create a ticket with a user not having Update  
>>> permissions.  Is this a problem?  Is there a doc which explains  
>>> read/write/edit/delete and update/assign permission description?
>>
>> Did you check that the type is setup for that queue properly? Check  
>> under WHups->Admin->Setup Queues and also the Queue/Type Matrix.
>>
>>
>> -- 
>> mike
>> The Horde Project
>> http://www.horde.org
>> https://www.facebook.com/hordeproject
>> https://www.twitter.com/hordeproject
>
>
> ----- End message from Michael J Rubinsky <mrubinsk at horde.org> -----
>
> I don't know how the problem got solved, but now, authenticated user  
> is able to select Ticket Type. The authenticated user is also able  
> to select Ticket State: Unconfirmed, Assigned, Accepted.  How to  
> make him not to use this option?
>


Just want to confirm, whether disabling selecting a ticket state at  
the time of creation of a new ticket is doable?  I tried out with some  
of the earlier suggestions posted in mailing list like 'enabling edit  
permission for guest and many other combinations of permissions'.  I  
could not succeed.

-- 
      सादर धन्यवाद/ Thanks & Regards
           अनंत / Anant
------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------