forked from City-of-Helsinki/respa
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release r45 #194
Merged
Merged
Release r45 #194
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a management command to send reservation reminders for reservations that start within 24 hours. Refs TTVA-219
…change TTVA-220 | Move Name and Description fields higher in resource form
TTVA-219 | Send reservation reminders
Add a new field `active` to the `Purpose` model. Admin users can change this field in Django admin. Hide inactive purposes from the resource form in the Respa admin. Refs TTVA-218
Add a new field `active` to the `TermsOfUse` model. Admin users can change this field in Django admin. Hide inactive terms of use from the resource form in the Respa admin. Refs TTVA-218
Add a new field `active` to the `ResourceType` model. Admin users can change this field in Django admin. Hide inactive resource types from the resource form in the Respa admin. Refs TTVA-218
Add a new field `active` to the `ReservationMetadataSet` model. Admin users can change this field in Django admin. Hide inactive reservation metadata sets from the resource form in the Respa admin. Refs TTVA-218
Add a new field `active` to the `Equipment` model. Admin users can change this field in Django admin. Hide inactive equipments from the resource form in the Respa admin. Refs TTVA-218
TTVA-218 | Add a possibility to hide selectable field values from the Respa admin
People capacity will be split into two fields: `people_capacity_lower` and `people_capacity_upper` for adding a possibility to define a range of the space capacity. Rename the `people_capacity` field to `people_capacity_lower` in the `Resource` model and keep the data of the original field in this new field. Keep the original name `people_capacity` in the API until UI changes are done. Refs TTVA-217
Add the field `people_capacity_upper` to the `Resource` model and to the Respa admin's resource form. Refs TTVA-217
Make sure that both `people_capacity_lower` and `people_capacity_upper` are considered when filtering resources by people capacity. Refs TTVA-217
TTVA-217 | Add a possibility to define a range for people capacity
When creating new order lines, use the tax class that is calculated in PriceList `get_price_info` method. Refs TTVA-224
Fix tax class in order creation
Hide the `people_capacity_upper` field from the Respa admin's resource form for now. TTVA-217
TTVA-217 | Hide people_capacity_upper from the Respa admin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.