Branch: refs/heads/ci-check-closed-flicker-issues Home: https://github.com/xwiki/xwiki-dev-llm Commit: 4b531c298512073d3cb4d1876a7be02c95d2dd47 https://github.com/xwiki/xwiki-dev-llm/commit/4b531c298512073d3cb4d1876a7be0... Author: Vincent Massol <[email protected]> Date: 2026-09-20 (Sun, 20 Sep 2026) Changed paths: M xwiki/okf/servers/jira.md M xwiki/scripts/jira-flickers.mjs Log Message: ----------- [Misc] Keep the flicker-lookup traps out of the always-loaded JIRA file okf/servers/jira.md is read whenever any JIRA topic comes up, and its declared scope is access, when to file at all, and the Component / Affects / Fix Version conventions. JQL quirks on one custom field and a de-duplication rule for a lookup are not that, and every session filing an ordinary bug was paying for them. * Move the two "Flickering Test" JQL traps into the header of jira-flickers.mjs, which is the file you are reading if you are about to get them wrong, and which costs nothing until you open it. Both consumers of the join (xwiki-ci-check, xwiki-release-test-triage) already go through it. * Leave one routing line in jira.md: use the shared module rather than writing the query. Routing is what actually prevents the mistake; the detail is not. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications