0037392: Users with "Reporter" access can't submit a bug report if they pick any product version at all - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0037392	mantisbt	other	public	2026-09-16 09:27	2026-09-17 05:24

Reporter	c_schmitz	Assigned To	atrol
Priority	normal	Severity	block	Reproducibility	always
Status	resolved	Resolution	duplicate
Product Version	2.28.4

Summary	0037392: Users with "Reporter" access can't submit a bug report if they pick any product version at all
Description	When reporting a new issue, users can pick a "Product Version" from a dropdown. For Reporters, that dropdown correctly only offers released versions — that part works fine. But when the report is actually submitted, the system rejects it, saying the version is invalid — even though it's a perfectly normal, released version that was legitimately offered in the dropdown. This only happens for accounts below "Developer" level (the default setting for who's allowed to report against unreleased versions). Administrators and Developers don't see this problem, so it's easy to miss unless you test as a lower-permission user.
Steps To Reproduce	1.) Use a project that has at least one released version. 2.) Log in as a user with "Reporter" access to that project. 3.) Open "Report Issue," select the project, and pick any version from the "Product Version" list. 4.) Fill in the rest of the form and submit. Expected result: The issue is created normally with the selected version. Actual result: Submission fails with "APPLICATION ERROR 0000029 — Invalid value for 'version'."
Additional Information	Where to look: validate() in core/commands/IssueAddCommand.php — it checks whether the user is allowed to report unreleased versions, but applies that check to every version, not just unreleased ones. I will submit a PR later, today.
Tags	No tags attached.

c_schmitz 2026-09-16 09:47 reporter ~0071445 Last edited: 2026-09-16 09:47	To me it seems this is already fixed in the master branch. Considering that this is such a wide-affecting blocker, why wasn't there a new version released already?

atrol 2026-09-16 16:21 developer ~0071449	why wasn't there a new version released already? There was a plan to release 2.29.0 some weeks ago, but that had to be postponed. @dregad FYI

dregad 2026-09-17 05:24 developer ~0071451	@c_schmitz indeed it's fixed in upcoming 2.29.0 (see 0037320) so no need to submit a PR. Release was planned for end of July, but unfortunately I could not finalize before going on vacation, then things happened and I had to postpone again. I don't want to make a hard commitment, but I hope to find the time in the coming days. Until then you can manually apply the patch in commit MantisBT master 4cfa980d.