Staff Slips
(UXPROD-19)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Staff Slips |
| Type: | New Feature | Priority: | P3 |
| Reporter: | julie.bickle | Assignee: | julie.bickle |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | staff_slips, staff_slips_tokens | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Release: | Not Scheduled |
| Epic Link: | Staff Slips |
| Development Team: | None |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R3 |
| Description |
|
Current situation or problem: End users assume that, if a token can be added to a staff slip, then the token will get populated with data when the slip is printed. However, there are cases where this is not the case, e.g. Hold expiration on a Pick slip, or Delivery address type on a Hold slip. Adding the concept of a Category, to filter the tokens accordingly (like is currently the case for patron notices) could solve this issue. In scope Out of scope Use case(s) Proposed solution/stories Links to additional info Questions |