Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Description Jira-tickets

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-1845

  • Probably, this issue comprises the following ones?


Jira Legacy
serverSystem JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-321

  • Proposals:
    • Additional facets
      • claim number (Mahnstufe) for SLUB Dresden
    • The CQL-search (exclusion of specific values, …) should be possible 

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-396

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-397

  • Proposals:
    • If the “Claiming setting” (-> see /wiki/spaces/~hohmann/pages/3572651) is implemented, the relations to the checkbox in POL must be defined: 
      • The value of the POL-checkbox is derived from the checkbox in the template 
      • The value of the POL-checkbox is a superior indicator which overrules the checkbox in the “claiming settings” -> If this checkbox is changed, the value in the settings is not regarded. 

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-398

  • Questions:
    • Is the screen shot in the ticket correct or is it the screen shot in UIOR-399?
  • Proposals:
    • Besides the “Expected receipt date”, the status of the order should be considered for the alert to prevent claiming of orders which are set from “open” to “pending”
      (
      -> See slide Description existing elements and values / App: Orders / “Status”).

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-399

  • Proposals:
    • It must be possible to show several claiming numbers and claiming processes in the POL
      (
      -> see /wiki/spaces/~hohmann/pages/3572651). 
    • For each claim, the date on which the claim was triggered, must be available.

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-498

  • Questions:
    • Is there more information? It is difficult to imagine the process. 
  • Proposals:
    • There should be an automatic or batch-option. It would be cumbersome, if each claim has to be sent to the vendor manually
      (
      -> See slides: /wiki/spaces/~hohmann/pages/3572653).

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUIOR-670

...