Why the status of an issue still can be changed directly?

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
lchydp
Posts: 38
Joined: 11 Apr 2013, 14:21
Location: China

Why the status of an issue still can be changed directly?

Post by lchydp »

Hello moderators,
I have set "Workflow Transitions" as below,
I think a bug whose status is "assigned" can't be changed to "resolved" directly.But I still can do it.Why :?:
Attachments
status.png
status.png (29.68 KiB) Viewed 3060 times
atrol
Site Admin
Posts: 8575
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: Why the status of an issue still can be changed directly

Post by atrol »

I was not able to reproduce your problem with a fresh install of the latest stable version of MantisBT (1.2.15 at the moment).

If you don't run 1.2.15 I recommend that you upgrade.
If you still get the issue running 1.2.15 you should provide detailed, step-by-step instructions to reproduce the issue. Additional information listed below may also be useful:

- Exact version of PHP, Database, Web server and Operating System
- Relevant customizations (e.g. changes in config_inc.php, etc)
- Installed plugins or custom functions ?
- Was the MantisBT source code modified in any way ?
Please use Search before posting and read the Manual
lchydp
Posts: 38
Joined: 11 Apr 2013, 14:21
Location: China

Re: Why the status of an issue still can be changed directly

Post by lchydp »

Thank you!I still use V1.2.14 because I haven't time to update MantisBT.I will upgrade it later.
The phenomenon I had observed was the settings in this page changed to the default values sometimes.
I found that I had modified this line in xampp\apache\conf\httpd.conf
Before modification:Listen 80
After modification:Listen mail.companyname.com:80
I have changed it back.Up to now,this problem hasn't occured.I will keep on observing it.If it occurs,I will consult you again.Thank you again. :)
atrol wrote:I was not able to reproduce your problem with a fresh install of the latest stable version of MantisBT (1.2.15 at the moment).

If you don't run 1.2.15 I recommend that you upgrade.
If you still get the issue running 1.2.15 you should provide detailed, step-by-step instructions to reproduce the issue. Additional information listed below may also be useful:

- Exact version of PHP, Database, Web server and Operating System
- Relevant customizations (e.g. changes in config_inc.php, etc)
- Installed plugins or custom functions ?
- Was the MantisBT source code modified in any way ?
Post Reply