Iteration 0.8.0-j (Friday Sept 7th, 2012)
1. Sprint Release (27th August 2012 - 7th Sept, 2012)
- 0.8.0-j
- Release date - Sept 7th, 2012
2. Tag Information
- SVN url for the released tag: https://svn.kuali.org/repos/ole/tags/ole-0.8.0-j
3. S&A Deliverables
S.No |
Type |
JIRA |
Summary |
Comments |
1 |
Task |
Work-in-progress on Gap Identified/mentioned/updates in Jira/Sub-task: https://jira.kuali.org/browse/OLE-3066 |
4. Deliver Deliverables
S.No |
Type |
JIRA |
Summary |
1 |
Task |
||
2 |
Task |
||
3 |
Sub Task |
||
4 |
Bug/Defect |
||
5 |
Bug/Defect |
Namespace, roles, permissions for Instance Maintenance documents in Rice2 not implemented |
5. Describe Deliverables
S.No |
Type |
JIRA |
Summary |
1 |
Bug/Defect |
6. Integration
S.No |
Type |
JIRA |
Summary |
Comments |
1 |
Task |
|
||
2 |
Other |
Convert existing services in docstore/discovery to RESTful API |
|
7. HTC Notes/Comments
Open Issues identified in JIRA OLE-3060 License Request (as per Sub-task OLE-3066)
SN |
Description & Steps |
1 |
GAP: Route Log on edocs- in Rice 1/KFS, the “Annotation” column displays the “Role Name” of the User who completed/is to complete the designated workflow. User Names alone do not communicate enough. Please add Role Name to Annotation column of e-doc Route Log - Need analysis to look into the framework code |
2 |
Currently for manual event logs the type is defaulted to User, rest of the event logs(file, agreement, location) are capture automatically by the system based on the event done on the screen, so do we still need a type dropdown where user wants to select different type and add the event log? |
Operated as a Community Resource by the Open Library Foundation