- Language: Ruby
- Stars: 447
- Repository: https://github.com/openfoodfoundation/openfoodnetwork
#4412## Description Missing translation: "END" in not translated in the date range selector, in Orders and Fulfillment (pic below). ## Expected Behavior It should appear translated to the chosen user language. ## Actual Behaviour END is shown, regardless of the choice of language. ## Steps to Reproduce 1. Login as an Enterprise/Hub. 2. Select a language other then English 3. Go to admin/reports/orders_and_fulfillment 4. The date range selector should show END, for the upper date limit. ## Animated Gif/Screenshot ![Screenshot at 2019-10-29 10-39-58.png](https://images.zenhubusercontent.com/5d761b049dde650001eaf32f/73ebbab5-3c57-45f0-9b93-a4aac9f9167f) ## Severity bug-s3: a feature is broken but there is a workaround ## Your Environment * Version used: v2.6.0 * Browser name and version: Chrome Version 78.0.3904.70 (Official Build) (64-bit) * Operating System and version (desktop or mobile): Ubuntu 18.04 Desktop
#4378## Description - As an Enterprise User - on the Orders page https://openfoodnetwork.org.au/admin/orders - I want to be able to see the Customer name without opening the order for editing. Often the email is not that useful for identifying the customer, and it is time-consuming to have to open orders to see who they are See discussion leading to this proposed solution here https://community.openfoodnetwork.org/t/enable-to-identify-customer-on-orders-view/1482/21 ## Acceptance Criteria & Tests As an Enterprise user managing orders, I can see the customer name for each order from Orders page, without having to open them to edit Suggested position under the email. ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/ef8df8b9-7bee-4d39-8b5f-d985c74651b5) The email and name text could/should be centrally vertically aligned within the row, same as other fields
#4377## Description - As an enterprise user - On page Orders (https://openfoodnetwork.org.au/admin/orders) - I want to be able to quickly capture payment on multiple orders, including where I have selected them according to filters see discussion at https://community.openfoodnetwork.org/t/enable-quick-capture-of-payments-for-a-batch-of-orders/1478/9 ## Acceptance Criteria & Tests Enterprise user should be able to set filters on the orders page to select a group of orders, and then 'capture payments' on these without losing their filter selection and being returned to home orders page each time Create multiple orders with cash payments i.e. order is complete but not paid. Orders that are complete but not paid have a small tick at the right hand side which allows the payment to be captured ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/65300e2d-95d2-4e13-8551-687f5e49d81b) Set filters to select the orders you are looking for e.g. all orders from a particular user, order cycle or distributor etc ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/ce412702-338f-4e05-b427-e35c7fa8d098) Hit capture payment button on the first order ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/9b0c2a8f-2158-4a60-83c3-9971ea8cda98) Page SHOULD NOT reload to Orders page with no filters selected. The capture payment action should take place while keeping the same selection of filters on the page. So the page should then look like this ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/43cd1548-d778-48e9-81ae-bb5de03ad2c3) [This should NOT happen] ![image.png](https://images.zenhubusercontent.com/54b83fb37c6ccc6277a6ea46/de778df8-5d58-4622-b094-13518793fd72)
#4304## Description When a user ships an order, the translation is set to "none" because the translation for shipment state is missing `= t(@order.shipment_state, scope: :shipment_states, default: [:missing, "none"])` ## Steps to Reproduce 1. Go to `/orders?q[s]=completed_at+desc` 2. Ship an order if none is shipped yet 3. Go to the edit order page ## Animated Gif/Screenshot ![image](https://user-images.githubusercontent.com/6525576/65441215-4fc7d600-de2a-11e9-947d-59fd56bd02da.png) ## Severity bug-s3: a feature is broken but there is a workaround ## Your Environment * Version used: v2.5 * Browser name and version: Freifox 69 * Operating System and version (desktop or mobile): Both
#3770## Description <!-- Describe the story in detail: **- As a:** (enterprise user, super admin, user...) **- On page:** (provide url of the page you want to modify. If not provide where will be created the new url and the name we want to give it) **- I want to be able to do:** (specify the desired behavior) (Link to others issues or resources to provide context > only if really necessary). --> As an enterprise user I want to be able to access my orders via the API. I want to be able to retrieve a set of completed orders that fall between two date-times. I want to be able to retrieve the set of orders for a specific enterprise. I want to only see orders for enterprises that I have appropriate permissions to view. This Swagger page documents the current OFN API. https://app.swaggerhub.com/apis/haseleyi/ofn-staging/0.1#/ However this documentation is incomplete. @kristinalim examined app/controllers/api/orders_controller.rb and found that actually there is much more flexibility. We would like to document and test this for the use case specified above. ## Acceptance Criteria <!-- Document the outcomes that need to be achieved before this component can be considered complete. --> To complete this issue please create a google doc with a set of test cases that demonstrate the API is working as intended. **Parameters:** - q[distributor_id_eq] - q[completed_at_gt] (greater than) - q[completed_at_lt] (less than) - q[state_eq] - q[payment_state_eq] - q[email_cont] (contains) **Results:** The API endpoint returns a JSON order as per the schema here:https://app.swaggerhub.com/apis/haseleyi/ofn-staging/0.1#/orders/get_orders The set of orders returned includes only orders with order.completed_at greater than or equal to start and less than or equal to end. The set of orders returned should only be orders for the enterprise matching the enterprise_id parameter. The set of orders returned must only include orders that the user has the authorisation to view based on their API key.