Page 1 of 1
Upgrade 1.2.8 to 1.2.15: Reporter not able to change status
Posted: 28 Aug 2013, 08:08
by bloombox
Hi,
after upgrading to version 1.2.15 a "Reporter" is no longer able to change status. We created a customized workflow which was working in previous versions. Now a "Reporter" has no possibility to change to one of the following status:
$g_set_status_threshold = array( PROPOSALACK => REPORTER,
ACKPRELIVE => REPORTER,
RESOLVED => REPORTER,
ABORTED => REPORTER,
NEW_ => REPORTER
);
The following status is defined whithin config_inc.php:
$g_status_enum_workflow[WAITPROPOSALOK]=
'38:proposalack,20:feedback,79:aborted';
I made a backup of the web folder and if I copy this back to "live" reporters are able to change to status "PROPOSALACK". Activating the update web folder of MantisBT Version 1.2.15 the reporter is no longer able to change status.
Any ideas? More information needed?
Best regards,
Jens
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 28 Aug 2013, 18:57
by atrol
Check / Set your configuration by using page Manage > Manage Configuration > Workflow Transitions
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 07:19
by bloombox
Hmm, I did that and from my point of view everything seems to be fine (as a matter of fact it worked before upgrading and I repeated the upgrade process two times to be sure that I didn't left anything open). Please have a look at the attached picture workflow.jpg.
- workflow.jpg (219.63 KiB) Viewed 12214 times
There you can see status "Waiting for approval by customer". Next status allowed are "Further Inquiry", "Approved by customer" (which is the default value) and "Cancelled". "Further inquiry" was not allowed for Reporters but the other two are (see second image, access_levels.jpg).
- workflow.jpg (219.63 KiB) Viewed 12214 times
Regards,
Jens
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 08:11
by atrol
Do you have more than one project?
Did you store your settings in database for a specific project or for "All Projects"
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 08:27
by atrol
Check also "Workflow Thresholds"
Do reporters have rights for "Update an issue"?
I assume no.
This might be the changed behavior between 1.2.8 and 1.2.15 as status changes need also "Update an Issue" right.
Maybe you want to try it, although this will provide more rights to your reporters than wanted by you.
This might be an unwanted side effect of another fix since 1.2.8.
I don't have time for more investigations at the moment.
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 09:03
by bloombox
Perfect, thank you very much: The hint to "Workflow Thresholds" and "Update an issue" did the job. I checked "Reporter" and now they are able again to accept/ approve changes.
- threshold.jpg (82.3 KiB) Viewed 12210 times
I will try to find out what "Reporter" are also enabled now.
Thank you very much for your really quick help!
Best regards,
Jens
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 09:10
by bloombox
Oh, yes, and we do have more than one project.
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 30 Aug 2013, 21:59
by atrol
bloombox wrote:
I will try to find out what "Reporter" are also enabled now.
This is what you changed by setting the "Update an issue" checkbox
Code: Select all
/**
* access level needed to update bugs (i.e., the update_bug_page)
* This controls whether the user sees the "Update Bug" button in bug_view*_page
* and the pencil icon in view_all_bug_page
* @global int $g_update_bug_threshold
*/
$g_update_bug_threshold = REPORTER;
Now your reporters are able to use the update page.
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 13 Sep 2013, 19:06
by atrol
I entered a report at
http://www.mantisbt.org/bugs/view.php?id=16376 for it.
Maybe you want to try my suggested fix.
Re: Upgrade 1.2.8 to 1.2.15: Reporter not able to change sta
Posted: 16 Sep 2013, 04:29
by clark99
faced the same issue
fix proposed at
http://www.mantisbt.org/bugs/view.php?id=16376
really fix it
thanks atrol!