Details
-
Type:
Rice Enhancement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: KR 2.5
-
Component/s: Unknown
-
Labels:None
-
Rice Theme:Usability
-
Priority Score:16
-
Functional Justification :Implementers have reported missing functionality and usability issues with KIM management screens.
-
Impact if not Implemented:Frustration for implementers and they may need to have developers go in the back end to set things up that are missing
-
Priority - KFS:Critical
-
Priority - KC:High
-
Priority - KS:High
-
Priority - Rice:Critical
-
Theme:Kuali Application Business Drivers
-
Application Impact:Low
-
Effort Estimate:Medium ~ 500 hrs
Description
First, a usability review and Functional Gap Analysis of KIM management screens needs to be performed to assess missing functionaity and determine usability issues. Anecdotal stories of difficulties have been reported to the Rice team and it needs further analysis outside of the comments on this Jira. Then the work to improve needs to be scheduled and completed.
Summary of Work Involved: The KIM screens are in dire need of a usability review as well as a gap analysis to see what functionality is missing from the current ones along with any new screens that should be added. The addition of KRAD to our toolbox should allow for a much better user experience. There would have to be some considerable analysis done ahead of time to layout what work needs to be done.
Attachments
Issue Links
- is related to
-
KULRICE-4137 Validations and labels for group qualfications not getting correctly picked up
-
- Open
-
-
KFSMI-5348 Validation of Document Type Name is not happening when assigning a role to a role.
-
- Open
-
-
KULRICE-4121 Cannot edit permission record with a namespace detail value that has wildcard
-
- Closed
-
-
KULRICE-4152 KIM allows you to create infinite loops of role memberships
-
- Closed
-
-
KULRICE-4153 Inactive qualifiers cause problems on existing roles
-
- Closed
-
-
KFSOLD-15466 Person: Cannot use hyphenated last name on the Person doc - receive error that only letters or digits may be used. Also prevents the addition of roles if a person comes into KIM via LDAP with a hyphen.
-
- Closed
-
-
KFSOLD-20193 Role document routes to EXCEPTION when adding assignees after inactivation of 'other' assignments when the role has associated qualifiers
-
- Closed
-
-
KULRICE-3969 Action policy code of ALL didn't work for responsibility assigned to a Group
-
- Closed
-
-
KULRICE-4122 When creating a new role or editing role the role description is not editable
-
- Closed
-
-
KULRICE-4136 Cannot edit any fields except active indicator on Group maintenance document
-
- Closed
-
-
KULRICE-4151 Permission and responsibility lookups don't seem to take nested roles into account
-
- Closed
-
-
KULRICE-4155 kim documents set boolean to on/off, rather than tru/false and do not use the boolean var/char converter to make Y/N in DB
-
- Closed
-
-
KULRICE-3898 Unable to add a Group to a Person via the Person document - access error received
-
- Closed
-
-
KULRICE-3970 Permission - unable to copy Permision "Create / Maintain Record(s)" - receiving error message that it may only consist of letters, digits, spaces or tabs.
-
- Closed
-
-
KULRICE-4154 Group document loses last added member when encountering an error
-
- Closed
-
-
KULRICE-4156 Required fields on group document not properly marked
-
- Closed
-
-
KULRICE-4157 the error message when a create / maintain record permission check fails when a document is submitted is really bad: business rule evaluation failed
-
- Closed
-
-
KULRICE-4175 Group Lookup - Group Name search is case sensitive
-
- Closed
-
-
KULRICE-4176 authorization error appears at the bottom of the Role document
-
- Closed
-
-
KULRICE-4177 Improve error handling on person doc when checking permissions for adding roles
-
- Closed
-
-
KULRICE-4178 Some role qualifiers displaying incorrectly
-
- Closed
-
-
KULRICE-3972 need to be able to sort by column header like on lookups when editing large roles and groups
-
- Closed
-
-
KULRICE-4174 Search on group by type throwing exception
-
- Closed
-
-
KULRICE-5197 Need to be able to sort by column header like on lookups when editing large roles and groups
-
- Closed
-
-
KULRICE-4179 enhance the responsibility document to automate changes to the location of action details
-
- Open
-
-
CONTRIB-47 Kuali Security Request Module
-
- Open
-
-
KFSOLD-20667 Need a document to feed data to the KFS-USER role
-
- Closed
-
- relates to
-
KFSMI-5329 LDAP and Role 54 - Role 54 is the KFS User Role and because it's pulling names from LDAP if there are several thousand, it is taking hours to load role 54 with 21000 employees.
-
- Rice Roadblock
-
-
KULRICE-4985 decouple non-people from people
-
- Open
-
-
KFSMI-5423 Creating a new Group: add text that a namespace must be chosen before group members can be added
-
- Rice Roadblock
-
- Trackbacks
-
Copy of Roadmap Draft 2 - Hampton Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
-
Kuali Rice Roadmap 2011 Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.1, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Kuali Rice Roadmap 2012 Draft Timelines The team is currently developing Rice 2.0 and is scoping Rice 2.2, which will be released approximately 6 months after the 2.0 Full Release. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2....
-
Roadmap Draft 2 Timelines The team is currently developing Rice 2.0. View a more detailed timeline and breakdown of Rice 2.0 features at KULRICE:Rice 2.0 Milestones. See details on our release cycles, i.e. frequency of major, minor,...
Specifically for this we are missing screens for creation of some things (like PermissionTemplates). Furthermore, the maintenance screens for creation of permissions and responsibilities are very primitive.