Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make bill recipient specific reporting optional #428

Open
tinne opened this issue Oct 5, 2020 · 0 comments
Open

Make bill recipient specific reporting optional #428

tinne opened this issue Oct 5, 2020 · 0 comments

Comments

@tinne
Copy link
Member

tinne commented Oct 5, 2020

Budgeteer currently only exports valid Budget reports if a custom Contract field rechnungsempfaenger exists. Nonwithstanding the non-standard spelling (Rechnungsempfänger means bill recipient) it created partial sums over all contracts in a project that relate to the same bill recipient.

This messy feature (cf. #427) needs to be cleaned up and standardized. I propose the following approach:

A project gets a new toggle Recipient Specific Billing. If unselected, Bill Recipient is a new mandatory text field on the project level. Else, Bill Recipients are edited on a per-Contract basis. The per-Contract bill recipient shall be entered via a combo box, i.e., while being able to add a new Recipient, the editor shall also be able to select one of the existing Recipients of the project from a dropdown list.

The Bill Recipient of a Contract (or of its Project, if not contract-specific) shall take the role the custom field rechnungsempfaenger currently has.

For backward compatility reasons, in a project with a custom field rechnungsempfaenger, the project toggle Recipient Specific Billing shall be force true, and the contract specific bill recipient shall be taken from the rechnungsempfaenger custom field, while the Bill Recipient field of the Contract remains unvisible.

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

No branches or pull requests

2 participants