Versions Compared

Key

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

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3435

Problem(s):

  1. Users are not easily able to export invoice data to run financial reports without a reporting tool

Use Cases & Requirements:

Ability to select
RequirementStatusUse cases
Ability to export invoices directly to csv

Status
colourYellow
titlePending

Our library staff always link invoices to an order, but I know from other libraries in our network that they don’t always link invoices to an order. So I think, an export of invoices in the Invoice App is also important.

Ability to pre-filter result set by specific criteria including Paid Date and Expense Class 

Status
colourYellow
titlePending

?

Need to filter for specific invoice data so that reporting out for different circumstances doesn't require additional labour intensive filtering of exported data.

The filters in the invoice app include paid date, which is not an option currently in the orders app.  If we were able to include (and filter by) invoice data, exporting from the order app would be fine.  Most times, we need to include payments from a precious invoice paid date range.

Ability to export invoice, invoice line, adjustment, and voucher field to include in the export, including title and price.Fund distributions and including title and price.

Status
colourYellow
titlePending

We need to have both PO/POL and INVOICE fields export into the same csv file.  It's vital for creating spreadsheets for corrections, such as fixing a payment that used the incorrect expense class.  Right now, we can identify the problem POLs that need to be 'unpaid' and 'repaid', but cannot provide invoice data needed for making the correction.


Include voucher data in export, voucher number, dispersement number, dispersement date

Status
colourYellow
titlePending

?
These exports could be used for following up on voucher export issues as well.

Incorporate invoice data into the existing order export functionality (See 

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-3466
) for more detail on this requirement

Status
colourYellow
titlePending

We need to have both PO/POL and INVOICE fields export into the same csv file.  It's vital for creating spreadsheets for corrections, such as fixing a payment that used the incorrect expense class.  Right now, we can identify the problem POLs that need to be 'unpaid' and 'repaid', but cannot provide invoice data needed for making the correction.

This is also essential for reporting out POL titles based on payment dates, and displaying paid amounts.

Update order filtering options to satisfy reporting from orders app (See

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-3466
)

Status
colourYellow
titlePending

The filters in the invoice app include paid date, which is not an option currently in the orders app.  If we were able to include (and filter by) invoice data, exporting from the order app would be fine.  Most times, we need to include payments from a precious invoice paid date range.


Proposed workflow:

Miro
AccessLinkhttps://miro.com/app/live-embed/uXjVOFcZRH4=?boardAccessToken=jTwvtXE3pHL25vIjNElTVIXy26f83zDf&autoplay=true
Height360
BoardTitleExport invoices in delimited file formate
Width640


Questions:

Questions

Status

Conclusions

Comments

Is the export of invoice records really necessary for operating functions?

Status
colourBlue
titleopen




Work Breakdown Structure:

Features:

Jira Legacy
serverSystem JiraJIRA
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyUXPROD-3435

UI Stories

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
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (UIOR, UIREC, UIV, UIF, UINV, UIORGS, STFORM, UIAC, UIPFO, UIPFCONT, UIPCITEM, UIPFINT, UIPFPOL))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc

MOD Stories

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
maximumIssues20
jqlQuery(issuekey in linkedIssues("UXPROD-3435") AND project in (MODORDERS, MODVEND, EDGOAIPMH, EDGORDERS, MODCRED, MODFISTO, MODFUND, MODGOBI, MODINVOICE, MODINVOSTO, MODOAIPMH, MODORDSTOR, MODREC, MODORGS, MODINV, MODCONF, EDGOAIPMH, mod-organizations-storage, mod-organizations, MODEBSNET))
serverId01505d01-b853-3c2e-90f1-ee9b165564fc