...
Info | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
General proposal
- When claims are filtered, it should be possible to create claim actions on several POL simultaneously. Otherwise, the claiming process is quite cumbersome.
- It is not to aim to create new actions, but only to apply them on several POL.
- To enable correct filtering, indicators for claiming are necessary, as for example
Jira Legacy server System JiraJIRA 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 UIOR-399 - Especially, when several claiming levels are implemented (/wiki/spaces/~hohmann/pages/3572651)
- If necessary, CQL-Search should be implemented to enable exclusion of specific elements.
- The ticket “create claim action” (
) must be regarded.Jira Legacy server System JiraJIRA 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 UIOR-670 - How can the proposed actions be applied to several POL or all filtered POL?
- After sending the claims, the date has to be captured in the POL.
- The creation of claim actions is only allowed for specific persons.
- The options for exporting the result-list can/must be analysed.
- The suggestions in the following mockups can be adjusted.
- All POL must be aggregated by “vendor” and “claim number”
- Otherwise, each POL is send in an own email/letter
...
- In the simple version, only a few actions are offered in the action box for the result list.
- “Start claiming process on result list” -> sending the claims to the vendor
- “Claim items report (CSV)” -> export of CSV-data to analyse and correct in Excel, …
- “Instanzen UUIDs” speichern -> export of UUID for reporting, …
- The actions of
are not implemented.Jira Legacy server System JiraJIRA 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 UIOR-670
...
- In the extended version 1, all actions of
are offered in the action box for the result listJira Legacy server System JiraJIRA 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 UIOR-670 - Delay claim
- Send claim
- Claimed at vendor system
- Add response
- Close claim
- Additional actions:
- “Claim items report (CSV)” -> export of CSV-data to analyse and correct in Excel, …
- “Instanzen UUIDs” speichern -> export of UUID for reporting, …
- The actions of
are not implemented.Jira Legacy server System JiraJIRA 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 UIOR-670
...
- In the alternative version 2, the link to the actions of
are offered in the action box.Jira Legacy server System JiraJIRA 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 UIOR-670 - “Create claim action (new window)”
- In the new “action window” the POL of the result list are shown not only one POL as in UIOR-670.
- Additional actions:
- “Start claiming process on result list” -> sending the claims to the vendor
- “Claim items report (CSV)” -> export of CSV-data to analyse and correct in Excel, …
- “Instanzen UUIDs” speichern -> export of UUID for reporting, …
- The actions of
are not implemented.Jira Legacy server System JiraJIRA 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 UIOR-670
...
- The claiming process is conducted in the app Receiving
- According to the options for the tables in the app Orders (Orders + Order lines), there should be two tables (order lines + Order items) in the app Receiving
- Order lines
- Order items
- The menu Action should be added with the claim option described in the proposals 1-3 above.
- It is then possible to conduct the claim for several levels for each item /wiki/spaces/~hohmann/pages/3572651
- Possible columns in the table "order items"
- Expected receipt date
- Received date
- Claim active
- It is necessary to extend the filter options for the claims in the app inventory according to the proposal for the app orders
Jira Legacy server System JiraJIRA 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 UIOR-321
...