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

implement a Team history page #3612

Closed
1 task
chadwhitacre opened this issue Jul 10, 2015 · 22 comments
Closed
1 task

implement a Team history page #3612

chadwhitacre opened this issue Jul 10, 2015 · 22 comments

Comments

@chadwhitacre
Copy link
Contributor

Reticketed from @mattbk at #3455 (comment), and somewhere else, too. :-)

Notify

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@blrhc
Copy link
Contributor

blrhc commented Jul 26, 2015

Definitely a good idea.

@chadwhitacre chadwhitacre added this to the Pivot milestone Sep 7, 2015
This was referenced Sep 7, 2015
@chadwhitacre
Copy link
Contributor Author

+1 @anselmh in #3756.

@chadwhitacre
Copy link
Contributor Author

Copying from @fenryxo at #3800 (comment):

[I]t would be great to have a dashboard similar to Patreon's one to provide teams with information about progress. For example:

  1. We are charging your patrons. It can take up to X days. $100 pledged by 25 patrons, $50 processed so far by 20 patrons.
  2. We are transferring money for payout. $100 pledged by 25 patrons, $80 processed by 23 patrons. (2 declined)
  3. We have sent you $90 ($10 fee). It can take up to X days. $100 pledged by 25 patrons, $80 processed by 23 patrons.

@chadwhitacre
Copy link
Contributor Author

@fenryxo Got a screenshot? :-)

@jiri-janousek
Copy link

Patreon - Dashboard
patreon_dashboard_0

Patreon - Patron Manager entry
patreon_manager_entry

Patreon - Transactions - example of in/out transaction pair (the worst case was 8 days delay)
patreon_transactions

@mattbk
Copy link
Contributor

mattbk commented Sep 30, 2015

I like this idea, but can we please have it be a table of some sort instead of a stream? It's easier to read if you are looking for errors, and easier to copy/paste out if you need to keep records.

@mattbk
Copy link
Contributor

mattbk commented Oct 1, 2015

From #3799:

[M]ight it make sense to have pledged donations show up in the history?

Yeah, I think so.

#3791 (comment)

It's confusing to users to see "receiving x.xx" but not get a payout of that amount every week. Adding pledged amounts to the history would alleviate this (but then we'd need to explain what pledges are).

@mattbk
Copy link
Contributor

mattbk commented Oct 1, 2015

How do we keep track of pledges right now? Is it just a table of tippee:amountperweek?

@chadwhitacre
Copy link
Contributor Author

@mattbk It's a due field in the payment_instructions table.

@mattbk
Copy link
Contributor

mattbk commented Oct 2, 2015

Note to self, look at whatever file does the calculations for for this

image

to better understand what could be pulled from for a history page. I may not be much help in implementing it, but I want to know how the db relationships work.

@chadwhitacre
Copy link
Contributor Author

+2 from @anselmh @book in #3756 for communicating due/owed on the Team history page.

@chadwhitacre chadwhitacre modified the milestones: Pivot, Team Basics Oct 29, 2015
@chadwhitacre
Copy link
Contributor Author

+1 @dcht00 in #3858.

@rohitpaulk rohitpaulk self-assigned this Dec 12, 2015
@chadwhitacre
Copy link
Contributor Author

Bump. One of four left on Finish Team Basics. You're self-assigned @rohitpaulk. Still interested?

@rohitpaulk rohitpaulk removed their assignment Apr 10, 2016
@rohitpaulk
Copy link
Contributor

I'm interested - but I've removed my assignment for now, so that someone else can pick it up if they want to before I get to it :)

@kaguillera
Copy link
Contributor

Considering taking this up... @rohitpaulk me know if you started it anything as yet.

@rohitpaulk
Copy link
Contributor

Haven't started @kaguillera :)

@kaguillera
Copy link
Contributor

So while working on this I realized that I need/should/want to clean/update fake_data.py so that I can visually design and test the page that this ticket should produce. So I am going to work on that first in a separate PR and then come back to this. Hopefully the fake_data.py cleanup should not take long.

Oh but I have started working on this...

@kaguillera
Copy link
Contributor

I just noticed #3596 and that I had this in mind before. So I will use this PR (hopefully) to make the necessary changes.

@kaguillera
Copy link
Contributor

Ok #3596 is up for review so I am coming back to this. I would like #3596 to be merged before I do this but I think that I can move ahead and make some progress in the mean time. So when #3596 does finally get merged this should be close behind.

@mattbk
Copy link
Contributor

mattbk commented Sep 22, 2016

#4128

@kaguillera
Copy link
Contributor

Thanks for the reference @mattbk I should have done that... 😦

@chadwhitacre
Copy link
Contributor Author

Moving to PR in #4128.

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

6 participants