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.
Users can't "Close" an issue in version 2.24.3
Moderators: Developer, Contributor
-
- Posts: 17
- Joined: 28 May 2018, 13:56
-
- Posts: 17
- Joined: 28 May 2018, 13:56
Re: Users can't "Close" an issue in version 2.24.3
Colleagues, any ideas?
Is it possible that custom role affect system behavior?
thx.
Is it possible that custom role affect system behavior?
thx.
Re: Users can't "Close" an issue in version 2.24.3
Perhaps a workflow has been activated on project level?
-
- Posts: 17
- Joined: 28 May 2018, 13:56
Re: Users can't "Close" an issue in version 2.24.3
No, see attached screenshots.
Re: Users can't "Close" an issue in version 2.24.3
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.
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.
-
- Posts: 17
- Joined: 28 May 2018, 13:56
Re: Users can't "Close" an issue in version 2.24.3
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
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.
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.
-
- Posts: 17
- Joined: 28 May 2018, 13:56
Re: Users can't "Close" an issue in version 2.24.3
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;
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;