Bug 631 - Add CSV output to budget-sync
Summary: Add CSV output to budget-sync
Status: RESOLVED FIXED
Alias: None
Product: Libre-SOC Organisation
Classification: Unclassified
Component: Planning (show other bugs)
Version: unspecified
Hardware: PC Linux
: High enhancement
Assignee: Jacob Lifshay
URL:
Depends on:
Blocks:
 
Reported: 2021-04-25 05:45 BST by Jacob Lifshay
Modified: 2022-02-24 20:39 GMT (History)
2 users (show)

See Also:
NLnet milestone: ---
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Lifshay 2021-04-25 05:45:02 BST
from lkcl:
nlnet is having difficulty keeping track of rhe task subdivision given that many different people contribute over time.
could you add CSV write to budgetsync which has, as columns, each person's amount, date requested, date paid, plus a "percentage" column showing how much of total has been paid for rhe task.
each Grant should have its own separate CSV file.
Comment 1 Jacob Lifshay 2021-09-22 05:33:28 BST
I pushed a fix for this, I adjusted the generated CSVs for milestones to include columns for:
budget_excluding_subtasks: value from bugzilla
budget_including_subtasks: value from bugzilla
fixed_budget_excluding_subtasks: value guessimated to hopefully be consistent
fixed_budget_including_subtasks: value guessimated to hopefully be consistent
submitted_excluding_subtasks: sum of all payments that are submitted and/or paid
paid_excluding_subtasks: sum of all payments that are paid

I also adjusted it to include all bugs that have payments and/or money assigned, rather than just those bugs with payments.

I'm assuming nlnet is quite capable of dividing one column by another to derive percentages (paid_excluding_subtasks * 100% / budget_excluding_subtasks)

lkcl, if you're happy with this, please mark this fixed
Comment 2 Jacob Lifshay 2022-02-24 20:39:09 GMT
assuming fixed since no one complained