[Savannah-hackers] [support #102576] [waiting for software update] Tech Only User is a m...

[Mathieu Roy]

This mail is an automated notification from the support tracker
 of the project: Savannah.

/**************************************************************************/
[support #102576] Latest Modifications:

Changes by: 
                Mathieu Roy <address@hidden>
Date: nttWed 11/26/2003 at 12:19 (Europe/Paris)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
              Status | Open                      | Closed







/**************************************************************************/
[support #102576] Full Item Snapshot:

URL: <http://savannah.nongnu.org/support/?func=detailitem&amp;item_id=102576>
Project: Savannah
Submitted by: Russell Smith
On: Mon 11/03/2003 at 11:22

Category:  Installation Process
Priority:  5 - Normal
Severity:  3 - Ordinary
Resolution:  Fixed
Assigned to:  yeupou
Originator Email:  
Status:  Closed


Summary:  [waiting for software update] Tech Only User is a m...

Original Submission:  
When a member has "Tech Only" permission for bugs, the

user does not get the privileges to alter the bugs. 

This is the desired behaviour.



However the do not even have access to alter bugs that

they are assigned.  I would think this is important, as

otherwise there is little value in having "Tech Only".  



This may be the desired functionality on savannah, but

I would like it to be different.  So when a "Tech Only"

user is assigned a bug, they have privileges to change

it, until such a time as it's not assigned to them

anymore.  But still not have any access to bugs that

are not assigned to them.



Thanks for you ongoing support on this free service.



Regards



Russell Smith

Follow-up Comments
------------------


-------------------------------------------------------
Date: Mon 11/10/2003 at 11:17       By: yeupou

Technicians will be    
allowed to change all fields but the    
priority/status/assigned_to fields (only trackers managers   
should be able to change that - manager is a replacement   
name for the confusing "admin" name, which is currently   
shown in the permission configuration page)   

-------------------------------------------------------
Date: Mon 11/10/2003 at 11:06       By: mr-russ

I am confused, can you please re-paste the strategy that

will be implemented for clarity.



Regards



Russell Smith

-------------------------------------------------------
Date: Mon 11/10/2003 at 10:05       By: yeupou

Hi,      
     
After discussion, we keep the first strategy mentioned.     
Not that yours does not make sense, but since this part is     
not configurable and would require lot of work to make it     
so, we have to select the solution that would satisfy most     
of the persons.     
   
This is already fixed in the CVS development branch but I 
let this item  pending until we actually run the dev 
branch on this server. 

-------------------------------------------------------
Date: Sat 11/08/2003 at 11:42       By: yeupou

Well, the idea in the end is to permit people to configure     
if technician can modify a field or not.     
    
But if someone wants to use the distinction    
Technician/Manager, it theoretically means that the    
technician should not be managing the bug report: and    
closing it is a way to manage it. The technician should    
use the resolution field to say "fixed", and then, the    
manager should decide whether he want to close the report    
or wait for user input or whatever.    
    
Your idea of giving management rights to someone if he got    
assignement of an item is interesting, however, and easy   
to implement. I'll talk about that with people at CERN on   
Monday, both solutions are sensitive.    

-------------------------------------------------------
Date: Sat 11/08/2003 at 11:29       By: mr-russ

I would specifically request that a tech be allows to change

the status.  It's ineffective if a tech cannot close the

bugs they fix.



I would suggest that they have manager rights, if and only

if they are the assigned technician.  But the better

solution is what you have suggested with the ability to

close a bug.

-------------------------------------------------------
Date: Sat 11/08/2003 at 10:42       By: yeupou

We noticed that strange behavior. I suppose that noone  
ever try to set someone as technician before.  
  
It is something hi work on currently: technicians will be  
allowed to change all fields but the  
priority/status/assigned_to fields (only trackers managers 
should be able to change that - manager is a replacement 
name for the confusing "admin" name, which is currently 
shown in the permission configuration page) 












For detailed info, follow this link:
<http://savannah.nongnu.org/support/?func=detailitem&amp;item_id=102576>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/