You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Although, the clothing feature is quite good already, I still have some feature requests (feel free, to split issue into more issues):
I would like to be able to model additional clothings in pyOphase for a better overview
After closing order possibilities, I want to be able to cancel orders and move them into the additional clothings (if people are not part of the Ophase anymore)
I want to be able to assign additional clothings to people (paid or free) to keep track of reservations of additional clouthings
I want to be able to export a ODS/XLSX and PDF of all orders with a table Size/Product containing the numbers. These should be 4 tables (ordered & paid, ordered & free, additional, total) in different tabs or among each other (maybe even with prices for the single tables).
These features would really enhance the clothing process and we would need much less paper lists.
I also have reference ODS files, if helpful.
The text was updated successfully, but these errors were encountered:
The term "additional clothings" means t-shirts etc. that are ordered by the head of ophase to pass them to tutors and orgas which did not register in time.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Although, the clothing feature is quite good already, I still have some feature requests (feel free, to split issue into more issues):
These features would really enhance the clothing process and we would need much less paper lists.
I also have reference ODS files, if helpful.
The text was updated successfully, but these errors were encountered: