Problem ReleaseNotes.Code.Change.ChangeTemplate sets audience to user but leaves importance empty, and the getChanges wiki macro declares its importance parameter with the default 0,1,2. A change whose importance was never set therefore matches no filter: it is stored, it is returned by {{GET /wikis/xwiki/releasenotes/ {product} / {version} /changes}}, and it is displayed by no release note and no custom report. This is not specific to the REST endpoints — the wiki UI, the Java API and the script service all create a change the same way. It was found on a wiki while checking RN-115: four user changes existed for a version, two showed on its release note. It is silent in both directions. An author who never opens the Importance field gets a change that vanishes; an agent posting changes over REST collects a 201 for each one and an empty release note. Fix Give ChangeTemplate an importance the way it already has an audience. Creation is template-driven for every caller, so one value fixes the UI, the Java API, the script service and the REST endpoints at once, and an author who does mean to change it still can. |
