Skip to content

fix: keep tags when saving them on a closed ticket - #398

Merged
Rom1-B merged 1 commit into
11.0/bugfixesfrom
fix/closed-ticket-tag-save
Oct 27, 2026
Merged

Rom1-B merged 1 commit into
11.0/bugfixesfrom
fix/closed-ticket-tag-save

Conversation

@Herafia

@Herafia Herafia commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !47169

On a closed ticket, the “Save Tags” button used to delete all tags. In GLPI 11, the ID of the multi-select field no longer matches the JS selector, so no value was being sent. The field is now identified via data-glpi-plugin-tag-dropdown-uuid, and the button has a tooltip.

Screenshots (if appropriate):

image

@Herafia
Herafia requested review from a team, Lainow, Mary-Clb and RomainLvr and removed request for a team October 26, 2026 14:23
@Herafia

Herafia commented Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

The partner approved the fix

@Rom1-B
Rom1-B merged commit b1dcf11 into 11.0/bugfixes Oct 27, 2026
7 checks passed
@Rom1-B
Rom1-B deleted the fix/closed-ticket-tag-save branch October 27, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants