...
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4186 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4134 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-1845 |
|---|
|
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-4168 |
|---|
|
Problem(s):
When user has made the decision to make a claim for a piece of material the user will be able to generate and share that information with the vendor
Claim information can differ from one library (agency) to the next and even based on order type
Claims require management over time, there are often multiple events that occur while working on a specific claim.
Requirements and Use Cases:
...
| Question | Status | Conclusion | Comments |
|---|
| Should claim forms be generated for a given order or a selection of orders? | |
|
|
| What order and receiving fields are required? | |
|
|
| Can you provide examples of your current claim form? For serials and for monographs | |
|
|
| Is there a use case in which in serials receiving a received issue does not trigger a claim for the prior unreceived issue? I.e., should receiving an issue automatically trigger a claim if the previous issue is unreceived? | |
|
|
| Is there a use case for searching open claims or viewing all open claims? | |
|
|
...