-
Notifications
You must be signed in to change notification settings - Fork 275
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
Allow to attach files (as proof of expense) #429
Comments
It's technically feasible, but I don't think this is the scope we want for this software. What's your usecase here? |
Just being able to attach proof to an expense (especially for large expenses). It's very convenient for roommate (anyone can therefore check the accounts and trust reign). I think it's a logical function for shared budget management software but it may not be the desired goal. |
Yep, one of the goals of IHM is to stay as simple as possible. Handling these pieces also means that the server contains a lot more valuable data than before. I'm +0 on this one. If anyone else thinks this is needed, don't hesitate to comment here :-) |
I agree with @almet. Another idea might be to add a new |
If that solves the problem for @Norde, why not! |
This would be a very good solution that would not weigh down HMI! |
@Norde are you willing to work on this? |
My knowledge of python is nil but I will take a look :) I think that the opening of a simple field "url" is within my capabilities. |
An optional field has been added to the bill form to add a link to a real bill. A new action button allow user to see this bill. Breaking change with Bill model update for database, a migration is needed. See issue spiral-project#429.
An optional field has been added to the bill form to add a link to a real bill. A new action button allow user to see this bill. Breaking change with Bill model update for database, a migration is needed. See issue spiral-project#429.
Could the possibility of attaching a file to an expense (like proof / invoice) be feasible?
The text was updated successfully, but these errors were encountered: