View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0014330 | mantisbt | customization | public | 2012-05-30 09:45 | 2012-06-16 06:34 |
Reporter | Nagendra Surya | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
Summary | 0014330: Customizing Status values | ||||
Description | I followed the instructions as per the link below http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php | ||||
Tags | No tags attached. | ||||
Attached Files | config_inc.php (248 bytes)
<?php $g_hostname = 'localhost'; $g_db_type = 'mysql'; $g_database_name = 'db_bug_tracker'; $g_db_username = 'root'; $g_db_password = 'passw0rd'; $g_allow_signup = OFF; $g_default_bug_view_status = VS_PRIVATE; $g_news_enabled = ON ; ?> | ||||
And? |
|
sorry it is not reflecting test |
|
Please be more specific.
|
|
I followed the Instructions as per the link http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php [^] But the newly created Status did not reflect in the application. |
|
As you are not providing any useful additional information, I am marking this as resolved. |
|
I apologize if i am not able to communicate properly. I followed the Instructions as per the below link TO ADD NEW BUG STATUS VALUE "TEST" http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php I expected "Test" to appear in view issue page, and status drop down. but it did not appear in any of the above expected places. |
|
I got the link the first time you posted it. That does not help, I know what the documentation says. What I need to know is exactly how you configured things in your system (--> upload or post relevant sections of your modified config files) and what errors/behavior you get (--> upload screenshots) Also note that this documentation link is for Mantis 1.0 - this section was actually updated recently, so you might want to check out the latest version from a nightly build http://mantisbt.org/builds/ |
|
I am not technically sound , so i was not able to understand what you wanted me to check out in nightly build. I have attached my existing config file. which i reused from my previous version (1.1.6). In the same file i copied the lines of codes from the initial link to add the Status but was not able get the expected result. |
|
Just telling you that there is a revised version of this doc, which is not yet available on mantisbt.org - but the one you're using is still valid for your purposes so it does not really matter.
As per documentation, I would expect to see <i>custom_constants_inc.php</i>, <i>config_inc.php</i> (including modified $g_status_enum_string and possibly $g_status_colors), <i>custom_strings_inc.php</i>; you need also to update your workflow as appropriate, either in config_inc.php or in the Manage Workflow Transitions page. The file you uploaded does not contain any configuration related to custom statuses... |
|
Uploaded files as requested |
|
I get an error message: Warning: Unterminated comment starting line 4 in ./custom_constant_inc.php Fixing the syntax error (add */ at end of line), then everything works as it should and I get the correct behavior |
|
I updated custom_constant_inc.php .Now it has only below code <?define ( 'TEST', 60 ); But still its not working |
|
Pls precisely define "not working" - maybe a screenshot would help |
|
Newly added status not reflecting in view issues . Screen shot attached (capture.png) |
|
Sorry but the attached 'Screenshot from 2012-06-01 14:39:50.png' is what I get using your config files on a fresh installation... No problems here, works as advertised. As you already reported 2 issues where your environment is not working properly, I'm afraid this is another case of your local setup causing issues. |
|
but the link tells me on how to add a new status value.And if i am not wrong it the result should be that new status should be created across application. As for the environment , I am using test environment which is perfectly fine. its the production environment you are refering. |
|
That's correct. Considering that all I did is deploying YOUR files on a fresh installation and it worked, I am 100% confident that the problem is related to local setup. Again, I suggest you try again a new installation (that's including blank db since you mentioned that you are upgrading). Actually you may also want to check if your db config table (Manage / Manage Configuration) is not by any chance overriding any of the settings you're trying to modify in the config file (status_enum_string, status_colors) as well as the workflow. |
|