Skip to content

Merge release/17.6 into dev#24034

Open
openprojectci wants to merge 24 commits into
devfrom
merge-release/17.6-20260701050353
Open

Merge release/17.6 into dev#24034
openprojectci wants to merge 24 commits into
devfrom
merge-release/17.6-20260701050353

Conversation

@openprojectci

Copy link
Copy Markdown
Contributor

Created by GitHub action

mrmir and others added 24 commits June 25, 2026 17:04
This got removed as a side effect of updating
`apply_default_time_filter_and_sort` in a previous commit
…t-off-on-desktop-and-mobile

[DREAM-702] Status labels are cut off on desktop and mobile
…etween-quick-filters-and-all-filters

[OP-19579] Harmonize behaviour between quick filters and "All filters"
* Fix Team planner disabled tooltip direction

* Open disabled-card tooltips to the right for work packages ending within the first three calendar days

* removing the unused workPackage.date fallback.
- https://community.openproject.org/wp/NEX-630
- building proppatch must not unescape the location value, as it is
  already unescaped. characters like '+' break the proppatch request
The "Logged for" cell rendered the numeric id via a hard-coded #<id>
format, bypassing the formatted_id accessor the rest of the app already
uses. The parallel work_package_id renderer is left as-is since it is
unreachable in the XLS export path.

COMMS-837
The "My time tracking" workweek calendar built each event's title and
work package link from the numeric id, so semantic identifiers never
appeared and links routed to /wp/<numeric id>. Use to_param and
formatted_id so the event links by display identifier; classic mode
output is unchanged.

COMMS-837
A recurring meeting series is exported as one master event using DTSTART and RRULE.
Individual meetings that differ from the schedule are exported as separate override events,
each tagged with a RECURRENCE-ID pointing at the original slot it replaces.

The problem: when someone changes the series schedule, we insert a new current_schedule_start date as DTSTART.
But the older meetings that already happened before that new start are still exported as overrides, with a RECURRENCE-ID sitting before DTSTART.

Strict clients like OX complain about this and fail the input

This fix adds those older dates back as RDATE entries on the master event.
RDATE means "this date is also part of the recurrence set, even though the RRULE wouldn't generate it."
Now the override has a real instance to atccept it.

What does not get an RDATE:
- Occurrences at or after the new DTSTART: the RRULE already covers them, so they're valid instances on their own.
- Cancelled occurrences: those use EXDATE (removal), the opposite
* Change highlighting mode for the project selector to let the server handle the highlighting

* Bump primer to 0.89.0
The sibling renderer to the cost-report fix still emitted the numeric id,
so the display identifier would be lost if that column is ever reused.
Output is unchanged in classic mode.
…admin-import-jira-2-run-new-via-http-method-import-jira-id-run-new

[SC-269] Backport #23993 to v17.6
…-set-permission-command

[NEX-630] Remove breaking unescape
…is-missing-in-xls-timesheets

Bug/COMMS-837: Use semantic work package identifier in time tracking exports
@openprojectci openprojectci added the create-merge-release-into-dev-pr Mark auto created PRs that will be auto closed too label Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

create-merge-release-into-dev-pr Mark auto created PRs that will be auto closed too

Development

Successfully merging this pull request may close these issues.

8 participants