Page 1 of 1
Users can't "Close" an issue in version 2.24.3
Posted: 02 Nov 2020, 15:51
by mnemonicator
Hello, after upgrade from 2.12 to 2.24.3 users who have "Developer" role let me know that they can't "Close" an Issue from status "Resolved".
I able to reproduce this error.
In a workflow transition settings all options are checked, access level to statuses "Resolved" and "Closed" set to Developer.
Is this bug or?
thank you.
Re: Users can't "Close" an issue in version 2.24.3
Posted: 12 Nov 2020, 09:25
by mnemonicator
Colleagues, any ideas?
Is it possible that custom role affect system behavior?
thx.
Re: Users can't "Close" an issue in version 2.24.3
Posted: 12 Nov 2020, 11:54
by cas
Perhaps a workflow has been activated on project level?
Re: Users can't "Close" an issue in version 2.24.3
Posted: 16 Nov 2020, 08:11
by mnemonicator
No, see attached screenshots.
- 2020_11_16_11_05_54.png (59.82 KiB) Viewed 5006 times
- 2020-11-16 11_08_22-Workflow Transitions.png (50.29 KiB) Viewed 5006 times
Re: Users can't "Close" an issue in version 2.24.3
Posted: 16 Nov 2020, 08:33
by atrol
Your screenshot shows settings for "All Projects"
The question was, if you changed on project level.
For that, select the affected project in the project selection on the right top of the page.
Re: Users can't "Close" an issue in version 2.24.3
Posted: 16 Nov 2020, 14:20
by mnemonicator
I understand question correctly, nothing is changed on project level. Just decided to show what we have on all projects level.
Re: Users can't "Close" an issue in version 2.24.3
Posted: 16 Nov 2020, 15:09
by cas
If you believe it is a bug , please report accordingly.
Then you better add an overview of the workflow settings both global and for the specific project where it is happening so the dev's can have a clear view of the situation.
Re: Users can't "Close" an issue in version 2.24.3
Posted: 16 Dec 2020, 20:01
by mnemonicator
Got a solution from bug report
This is driven by the bug's read-only status, as defined by $g_bug_readonly_status_threshold (defaults to RESOLVED).
$g_update_readonly_bug_threshold then defines who is allowed to update read-only bugs (defaults to MANAGER)
So, with default settings (which seems to be what you have, based on the screenshots you uploaded), DEVELOPER is not allowed to update Readonly issues, and therefore can't close them.
as a result, variable $g_bug_readonly_status_threshold set to CLOSED;