-
Notifications
You must be signed in to change notification settings - Fork 548
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
Custom date range Field (for invoice and quote line items) #665
Comments
@Civolilah to support this particular feature across quotes/invoices/credits/purchase_orders we'll use the following format: ?date_range=column,start_date,end_date
For this particluar filter, we should not store these in the react settings or persist across sessions. |
Any traction on this feature request? also, for some reason this feature request is hidden (for me any way), and doesn't even show up in my activity profile. I am only able to go to this via an email link I had. |
@hermitdafunk This feature should be available for you in the Invoices entity table. By clicking on the "Calendar" icon, you will get the picker for selecting the date range. Screenshot: |
Sorry mate, where? (I am using flutter UI) and by looking at your screenshot it seems not to be inline with this specific feature request. Thanks man. |
@hermitdafunk Ah, you are using the Flutter app UI. The screenshot comes from React, as it is implemented on the React UI. I'm sure that @turbo124 or @hillelcoren can help you better with the Flutter app UI for this feature request. |
Note: in the Flutter app it's possible to filter by a date range in the reports. We'll look into also supporting this in the entity tables. |
Invoice Ninja Version:
v5.7.46-C123 (self-Hosted)
Environment:
Docker
Have you searched existing issues/requests:
Yes, I apologies if I have missed an existing feature request.
Screenshots
Additional context
https://forum.invoiceninja.com/t/is-it-possible-date-range-custom-field/12184
Thank you.
kind regards,
The text was updated successfully, but these errors were encountered: