Implementation/STC-783: Adapt PDF export of timesheets for semantic identifiers - #23712
Merged
akabiru merged 1 commit intoJun 12, 2026
Conversation
The work package column hardcoded the numeric id. Using formatted_id renders the project-based identifier in semantic mode.
akabiru
deleted the
implementation/stc-783-adapt-pdf-export-of-timesheets-for-semantic-identifiers
branch
June 12, 2026 14:09
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Ticket
https://community.openproject.org/wp/STC-783
What are you trying to accomplish?
On instances configured with project-based work package identifiers, the timesheet PDF export still showed the numeric database id in the work package column. The column now renders the configured identifier, so an entry exports as
PROD-42 Improve onboarding flowrather than#65 Improve onboarding flow.Screenshots
Before (classic identifiers)
stc783-timesheet-classic-before.pdf
After (semantic identifiers)
stc783-timesheet-semantic-after.pdf
What approach did you choose and why?
Same approach as the meeting PDF exports (#23708): the work package cell built its label from the raw numeric id, while the rest of the application renders identifiers through
formatted_id, which returns the hash-prefixed numeric id in classic mode and the project-based identifier in semantic mode. The cell label now goes through that method; classic-mode output is unchanged, and the link URL already resolved to the configured identifier through the URL helpers.Merge checklist