Versions Compared

Key

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

...

  • Ability to define filter criteria for …

    • Revenue types (including custom revenue types)

    • Expense types (including custom expense types)

  • Ability to search the transaction list for any visible attributes of the transaction (e.g. name, type, amount)

  • Top level indicators clearly defining …

    • Current revenues & projected revenues matching the filter criteria

    • Current expenses & projected expenses matching the filter criteria

    • Current profit / loss and projected profit / loss matching the filter criteria

  • A table showing all transactions (revenue and expenses) matching the filter criteria

    • Ordered in reverse chronological order

    • Clicking the head for each column reverses the sort order

    • Crop sales should be specially “bundled”

      • Custom revenue types that indicate a crop should be included in crop sales bundle

    • Labour expenses should be specially “bundled” such that all labour expenses for a given day are shown together

Nice-to-have:

  • Ability to define filter criteria for amount of transaction, setting both upper and lower bound

  • Adaptive design (as opposed to responsive), e.g.

    • Ability to view additional columns on Desktop vs. mobile

    • Differing indicator layout based on screen dimensions

  • Spotlight for how bundles work

  • “Drawer” filter design

  • Expanding and withdrawing search bar design

User interaction and design

...

Question

Answer

What is the general pattern for each line item on the Financials dashboard?

Headers:

Mobile ☝️

Desktop ☝️

Line items:

If expense:

  • Transaction => Item name (& “Date” for mobile)

  • Type => Expense type

  • Amount => Amount (shown in red and with negative sign if expense)

If revenue:

  • Transaction => Customer (& “Date” for mobile)

  • Type => Revenue type

  • Amount => Amount (shown in green and with positive sign if expense)

Does it makes the most sense to aggregate all crop sales for a particular day together into one “bundled” item, rather than displaying them as potentially dozens of individual transactions on the same day?

No! Reasoning is that the user can already add as many crops to each instance of the crop sale revenue as they would like. Our bundling on the finances dashboard should mirror the way the user creates the revenue. (this is a change Loic Sans )

How should crop sale bundles be displayed?

“Transaction” = <Customer> & <Date>

“Type” = “Crop sale” (In the general case the type of revenue or expense)

Does it makes the most sense to aggregate all labour expenses for a particular day together into one “bundled” item, rather than displaying them as potentially dozens of individual transactions on the same day?

Yes! The existing screens to view labour expenses by person or task lend themselves well to daily bundles (though “View all labour expenses >” should be removed).

What does the “>” arrow on each line item do?

For individual expenses and revenues, it navigates them to the read-only detail page for that transaction. For labour expense “bundles” it navigates them to the existing labour expense homepage.

update -Loic Sans is looking at a different icon or method than “>” to do this, but the user does need the ability to access the read-only detail page from the Finances dashboard

For crop sales with “…” “+ X”, how would we view those additional lines?

Loic Sans

update - For crop sale, it would navigate them to the crop sale read only detail page.

For labour expenses, it would navigate the user to the labour expenses page.

Out of scope

  • Clickable indicators