Issue 1463 - Can't use non requestable roles
Summary: Can't use non requestable roles
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Upgrade (show other issues)
Version: current
Hardware: All All
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-13 22:01 UTC by stx123
Modified: 2013-08-07 15:24 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description stx123 2001-08-13 22:01:11 UTC 
I made the role "developer" non requestable.
Now I'm not able to add new members with the developer role to projects.
Comment 1 Unknown 2001-08-14 00:01:44 UTC 
From our roles & resources lead engineer:

This is the expected servlet behavior as it is currently written. 
There are two template files, called ProjectRoleRequest and 
ProjectMemberAdd, in the core product. These use the same 
method: requestedroles(). Currently, ProjectMemberAdd calls 
this method when presenting the form-field list: it only shows 
requestable roles. This may be expected, but it is nonintuitive.

We are changing the ProjectMemberAdd template so that it 
displays not requestedroles but roles. So that list will show all 
available project roles. Looking for completion on this by the end 
of the day (PDT) Tuesday 14 August.
Comment 2 Unknown 2001-08-16 17:21:21 UTC 
Complete Wednesday 15 August .
Comment 3 stx123 2001-08-16 18:23:46 UTC 
verified ok
Comment 4 michael.bemmer 2003-03-13 11:08:14 UTC 
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.