INVOICE: do not use activity name as fallback for description #4884
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.
Description
Currently an empty description in a timesheet (and expense) causes Kimai to inject the activity name as invoice variable
entry.description
in the default calculator (one row per entry).This makes it impossible to detect whether the description was set or not and apply custom fallback logic.
This was removed: the field
entry.description
contains now the content from the timesheet. If empty then this field is empty as well.A replacement field was added called
entry.description_safe
which will use the activity name as fallback and if that is empty the project name.This is technically both a bug fix and BC break.
Types of changes
Checklist
composer code-check
)