[KULRICE-9862] Identify permission gaps between KNS and KRAD inquiry features Created: 03/Jul/13  Updated: 21/Apr/14  Resolved: 13/Jan/14

Status: Closed
Project: Kuali Rice Development
Component/s: Analysis, Roadmap
Affects Version/s: None
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Claus Niesen Assignee: Peter Giles (Inactive)
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-9863Identify inquirable gaps between KNS and KRAD inquiry features
KULRICE-9275Identify feature gaps between KNS and KRAD inquiry features
KULRICE-8800Identify gaps between KNS and KRAD lookup features
KULRICE-8792Perform analysis of the KNS inquiry framework
KULRICE-10744Create database scripts for KNS/KRAD conversion
KULRICE-9133Convert External Identifier Type to KRAD
KULRICE-8915Other Lookup Features
KULRICE-13568Create a smoke test for KRAD maintenance documents permission features
KULRICE-10257Implement support for inquiry in conversion scripts
KULRICE-4772Sections on direct inquiries have blank gaps between sections
Epic Link: Inquiry Equivalence
Rice Module:
KRAD Feature Area:
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:


Check if the permission checks in the Gap Analysis - Inquiry are implemented in KRAD.

Create a copy of the Gap Analysis Template and link to it from the Gap Analysis - Inquiry page.

Use the equivalency checklist as a guide.

Comment by Claus Niesen [ 30/Sep/13 ]

Peter: see Dan's email from 9/9/13

Comment by Claus Niesen [ 13/Jan/14 ]

Completed via individual feature analysis jiras.

Generated at Wed Apr 08 12:27:36 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.