Skip to content

Merge release/17.8 into dev - #24952

Open
openprojectci wants to merge 33 commits into
devfrom
merge-release/17.8-20260826034928
Open

Merge release/17.8 into dev#24952
openprojectci wants to merge 33 commits into
devfrom
merge-release/17.8-20260826034928

Conversation

@openprojectci

Copy link
Copy Markdown
Contributor

Created by GitHub action
Replaces #24927

tinexw and others added 30 commits August 10, 2026 11:28
Updated Jira import support details in README.md to clarify that Jira Server and Cloud are not supported, and added information about potential future support for Jira Server.
* 17-8-release-notes-draft

* Update README.md

* update

* update

* update

* Update docs/release-notes/17-8-0/README.md

Co-authored-by: dominic-braeunlein <d.braeunlein@openproject.com>

* Update README.md

* Update docs/release-notes/17-8-0/README.md

* Update docs/release-notes/17-8-0/README.md

Co-authored-by: Bruno Pagno <b.pagno@openproject.com>

* Update docs/release-notes/17-8-0/README.md

Co-authored-by: Bruno Pagno <b.pagno@openproject.com>

---------

Co-authored-by: dominic-braeunlein <d.braeunlein@openproject.com>
Co-authored-by: Bruno Pagno <b.pagno@openproject.com>
…ally-offscreen-on-work-package-description

[OP-19932] Ckeditor toolbar is partially offscreen on work package description
* XWiki setup link didn't lead to XWiki setup docs
* "More information" link in health check always pointed to storages
Co-authored-by: Maya Berdygylyjova <MayaBerd@users.noreply.github.com>
Using this to end the series via the API brings notification handling
for free.
add placeholder images to release notes
…g-notification-mails-via-the-api

[MEET-583] No way to send meeting notification mails via the API
Update Jira Server support details in FAQ
akabiru and others added 3 commits August 25, 2026 18:58
…24702)

Adds a system admin guide page that links to the versions and categories settings screen and the enable confirmation dialog. It covers changes to the Version field, manual conversion options, the impact on existing data, and API client information about the targetVersions collection.

https://community.openproject.org/wp/COMMS-951

---------

Co-authored-by: Maya Berdygylyjova <MayaBerd@users.noreply.github.com>
@openprojectci openprojectci added the create-merge-release-into-dev-pr Mark auto created PRs that will be auto closed too label Aug 26, 2026
@github-actions

Copy link
Copy Markdown

Warning

Flaky specs

  • rspec ./modules/backlogs/spec/features/inbox_column_spec.rb[1:7:1]
  • rspec ./spec/features/work_packages/table/switch_types_spec.rb[1:1:2]
🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #24952, linked for reference only):

- `rspec ./modules/backlogs/spec/features/inbox_column_spec.rb[1:7:1]`
- `rspec ./spec/features/work_packages/table/switch_types_spec.rb[1:1:2]`

Treat this as a standalone task, unrelated to PR #24952. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #24952 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @openprojectci to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @openprojectci, and request a review from @openprojectci.
On every commit, set @openprojectci as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.

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.