| Date | Product Owner | Notable Risks, Issues and/or Changes |
|---|
| 2018-11-05 | | - Split Requests Permissions into Requests Permissions (Simple) (UXPROD-1279, targeted for Q4) and Requests Permissions (Advanced/Action-Based) (UXPROD-236). This is because:
- We need to get at least a basic requests permission functioning for Chalmers. The more granular permissions can wait.
- Also, since the basic permission is UI-only, we should be able to squeeze it in given the UI devs are often blocked on backend work
- Finally, the more granular/advanced requests permissions are (to some extent) blocked awaiting "Action-Based Permissions" design and implementation (FOLIO-1504)
- Added Requests: access to list of requests via links in the item detail and user detail (UXPROD-235) to Q4 as it was UI-only and we had excess UI dev capacity on the Core team while blocked awaiting backend work.
|
| 2018-10-26 | Emma Boettcher | - Split Permissions into Permissions (Simple) (UXPROD-238, targeted for Q4) and Permissions (Advanced/Action-Based) (UXPROD-1251)
|
| 2018-10-19 | | - Still finalizing UI screens for Data Import mappings and logs.
- Many revisions/refinements to overall Data Import architecture document and diagrams, based on feedback from Lead Architects.
- Discussions with several related POs & Dev teams to determine responsibility for cross-app issues (e.g. File upload, ISBN handling rules)
|
| 2018-10-16 | | - Have added some ui-only stories to the Core team backlog which weren't originally targeted for Q4 because UI developers were blocked awaiting backend support:
| Jira Legacy |
|---|
| server | System Jira |
|---|
| jqlQuery | project = uxprod AND type = "new feature" AND (resolution not in (duplicate, "Won't Do") OR resolution is EMPTY) AND labels != NFR AND fixVersion was "Q4 2018" ON (2018-10-16) ORDER BY cf[10002] ASC, assignee ASC, summary ASC |
|---|
| count | true |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
|
|
| 2018-10-09 | | - Requests - Have implemented a simple filter of the Requests app for a v1 requests queue ( UIREQ-122). Dedicated request queue page (UIREQ-112) has been deferred
- Locations and service points
- Switching direction of the relationship. No longer support adding locations to service points. Instead, service points will be added to locations (to ensure each location has at least one primary SP)
- May have time to pick up some of the lower priority UX improvements for Location CRUD, as they are UI only and many other stories are blocked awaiting backend support: UIORG-92, UIORG-93, UIORG-94, UIORG-117.
|
| 2018-10-05 | | 4 new features added since last week. I have been working with Zak on a Q3 2018 bug (UIU-662) that appears to only happen on my laptop--we still want to figure out why because I need to be able to test with my laptop plus other FOLIO users may encounter the same problem. The UNAM developers are working on small bug fixes and tasks while Kimie designs the Patron Block and Transfer screens. |