-
Notifications
You must be signed in to change notification settings - Fork 5
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
Enhancement - Add a default Invoice Terms field to autopopulate in new invoices #21
Comments
FYI. Feature we currently offer based on the hour registration: |
Activated same feature for By setting |
Considering ticket closed. |
This is good to know, however I feel as a user you should make a clear distinction between what will fields will be client-facing and which will not. |
Ahh now I understand what you mean. Discusson on 'note' Stuff I'm using the Terms to me feels like the wrong name for this behaviour? Feature to add comment-field for internal use |
Discussion - I was also curious if the ability on the Invoices tab to add/import/link items from the Hour Registration tab would help, because then you don't have to copy the description across both tabs? |
awesome! regarding what to call the Note field, i willl leave that to you to decide, but just be cautious that standard invoice terms text are very commonplace on many company invoices and it is different from NotesToClient (relating to one specific invoice) and this is also different from NotesForMyself which is just for the user. |
Currently, when creating invoices the user has a "Notes" field where they can add any relevant notes relating to the current invoice.
As a user, I would like to be able to set a default "Invoice Terms" text field in my settings which are automatically populated at the bottom of each invoice I create.
The value added would be that it saves the user time from having to manually paste the terms of an invoice into every invoice that is created.
It could be achieved by adding another directive in the entities.toml file
The text was updated successfully, but these errors were encountered: