Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

improve team receiving page #3992

Closed
chadwhitacre opened this issue Apr 9, 2016 · 3 comments
Closed

improve team receiving page #3992

chadwhitacre opened this issue Apr 9, 2016 · 3 comments

Comments

@chadwhitacre
Copy link
Contributor

Reticketing from #3705 (comment):

I've started work on the receiving pages for teams at #3873. To convey the charging in arrears concept effectively, we'll need a proper overhaul of the way we present information -

I'm thinking of something like this - (taken from Harvest)

gratipaydemo

We'll have to tackle #3851 first though.

@chadwhitacre chadwhitacre added this to the Finish Team Basics milestone Apr 9, 2016
@chadwhitacre
Copy link
Contributor Author

  • fold "___ receives $X per week from Y ~users." into the charts:
    • fold "Estimated payment for next week" into the "DOLLARS RECEIVED PER WEEK" chart as a new bar on the right (maybe blue or red?)
    • add estimated number of payments into the "NUMBER OF PAYMENTS PER WEEK" chart as a new bar on the right (maybe blue or red?)
  • flag the right-most (new "estimate") bar by default on both "DOLLARS RECEIVED" and "NUMBER OF PAYMENTS", rather than the max.
  • drop "Dues"
    • fold "Funded Dues" into the "PER WEEK" charts, by adding bars for future weeks in which the payments are expected to come due.
    • replace "Unfunded Dues" with new "DOLLARS LOST PER WEEK" and "NUMBER OF FAILED PAYMENTS PER WEEK" charts (show just new failures per week, not accumulated failures)
  • replace "PAYMENTS RECEIVED, BY NUMBER OF PAYMENTS" with "NUMBER OF WEEKLY PAYMENTS BY AMOUNT" from /about/stats
  • replace "PAYMENTS RECEIVED, BY DOLLAR AMOUNT" with "SUM OF WEEKLY PAYMENTS BY AMOUNT ($)" from /about/stats

@chadwhitacre
Copy link
Contributor Author

That should probably be multiple PRs. :]

@chadwhitacre
Copy link
Contributor Author

Dropping from Finish Team Basics. What we have with #3873 qualifies for "Basics."

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant