0014330: Customizing Status values

(0031928)
dregad (developer)
2012-05-30 09:56

And?

(0031929)
Nagendra Surya (reporter)
2012-05-30 10:15
edited on: 2012-05-31 03:54

sorry it is not reflecting test

(0031930)
dregad (developer)
2012-05-30 11:07

Please be more specific.
- configuration changes you made
- error messages
- expected vs actual results (use screenshot if needed)

(0031937)
Nagendra Surya (reporter)
2012-06-01 03:07
edited on: 2012-06-01 03:08

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.

(0031938)
dregad (developer)
2012-06-01 03:09

As you are not providing any useful additional information, I am marking this as resolved.

(0031940)
Nagendra Surya (reporter)
2012-06-01 03:42
edited on: 2012-06-01 03:46

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.

(0031941)
dregad (developer)
2012-06-01 04:15

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/ [^]

(0031943)
Nagendra Surya (reporter)
2012-06-01 05:01

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.

(0031947)
dregad (developer)
2012-06-01 05:38

> was not able to understand what you wanted me to check out in nightly build.

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.

> I have attached my existing config file. which i reused from my previous version (1.1.6).

As per documentation, I would expect to see custom_constants_inc.php, config_inc.php (including modified $g_status_enum_string and possibly $g_status_colors), custom_strings_inc.php; 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...

(0031951)
Nagendra Surya (reporter)
2012-06-01 07:05

Uploaded files as requested

(0031954)
dregad (developer)
2012-06-01 07:55

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

(0031957)
Nagendra Surya (reporter)
2012-06-01 08:11

I updated custom_constant_inc.php .Now it has only below code

<?define ( 'TEST', 60 );
?>

But still its not working

(0031958)
dregad (developer)
2012-06-01 08:21

Pls precisely define "not working" - maybe a screenshot would help

(0031959)
Nagendra Surya (reporter)
2012-06-01 08:34

Newly added status not reflecting in view issues . Screen shot attached (capture.png)

(0031960)
dregad (developer)
2012-06-01 08:43

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.

(0031961)
Nagendra Surya (reporter)
2012-06-01 08:59

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.

(0031962)
dregad (developer)
2012-06-01 09:25

> And if i am not wrong it the result should be that new status should be created across application.

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.

Notes
(0031928) dregad (developer) 2012-05-30 09:56	And?

(0031929) Nagendra Surya (reporter) 2012-05-30 10:15 edited on: 2012-05-31 03:54	sorry it is not reflecting test

(0031930) dregad (developer) 2012-05-30 11:07	Please be more specific. - configuration changes you made - error messages - expected vs actual results (use screenshot if needed)

(0031937) Nagendra Surya (reporter) 2012-06-01 03:07 edited on: 2012-06-01 03:08	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.

(0031938) dregad (developer) 2012-06-01 03:09	As you are not providing any useful additional information, I am marking this as resolved.

(0031940) Nagendra Surya (reporter) 2012-06-01 03:42 edited on: 2012-06-01 03:46	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.

(0031941) dregad (developer) 2012-06-01 04:15	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/ [^]

(0031943) Nagendra Surya (reporter) 2012-06-01 05:01	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.

(0031947) dregad (developer) 2012-06-01 05:38	> was not able to understand what you wanted me to check out in nightly build. 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. > I have attached my existing config file. which i reused from my previous version (1.1.6). As per documentation, I would expect to see custom_constants_inc.php, config_inc.php (including modified $g_status_enum_string and possibly $g_status_colors), custom_strings_inc.php; 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...

(0031951) Nagendra Surya (reporter) 2012-06-01 07:05	Uploaded files as requested

(0031954) dregad (developer) 2012-06-01 07:55	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

(0031957) Nagendra Surya (reporter) 2012-06-01 08:11	I updated custom_constant_inc.php .Now it has only below code <?define ( 'TEST', 60 ); ?> But still its not working

(0031958) dregad (developer) 2012-06-01 08:21	Pls precisely define "not working" - maybe a screenshot would help

(0031959) Nagendra Surya (reporter) 2012-06-01 08:34	Newly added status not reflecting in view issues . Screen shot attached (capture.png)

(0031960) dregad (developer) 2012-06-01 08:43	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.

(0031961) Nagendra Surya (reporter) 2012-06-01 08:59	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.

(0031962) dregad (developer) 2012-06-01 09:25	> And if i am not wrong it the result should be that new status should be created across application. 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.

Issue History
Date Modified	Username	Field	Change
2012-05-30 09:45	Nagendra Surya	New Issue
2012-05-30 09:56	dregad	Note Added: 0031928
2012-05-30 10:15	Nagendra Surya	Note Added: 0031929
2012-05-30 11:07	dregad	Note Added: 0031930
2012-05-30 11:07	dregad	Status	new => feedback
2012-05-31 03:54	VishalThakur	Note Edited: 0031929	View Revisions
2012-06-01 03:07	Nagendra Surya	Note Added: 0031937
2012-06-01 03:07	Nagendra Surya	Status	feedback => new
2012-06-01 03:08	Nagendra Surya	Note Edited: 0031937	View Revisions
2012-06-01 03:09	dregad	Note Added: 0031938
2012-06-01 03:09	dregad	Status	new => resolved
2012-06-01 03:09	dregad	Resolution	open => unable to reproduce
2012-06-01 03:09	dregad	Assigned To	=> dregad
2012-06-01 03:42	Nagendra Surya	Note Added: 0031940
2012-06-01 03:42	Nagendra Surya	Status	resolved => feedback
2012-06-01 03:42	Nagendra Surya	Resolution	unable to reproduce => reopened
2012-06-01 03:43	Nagendra Surya	Note Edited: 0031940	View Revisions
2012-06-01 03:46	Nagendra Surya	Note Edited: 0031940	View Revisions
2012-06-01 04:15	dregad	Note Added: 0031941
2012-06-01 04:51	Nagendra Surya	File Added: config_inc.php
2012-06-01 05:01	Nagendra Surya	Note Added: 0031943
2012-06-01 05:01	Nagendra Surya	Status	feedback => assigned
2012-06-01 05:38	dregad	Note Added: 0031947
2012-06-01 07:05	Nagendra Surya	File Added: config files.zip
2012-06-01 07:05	Nagendra Surya	Note Added: 0031951
2012-06-01 07:55	dregad	Note Added: 0031954
2012-06-01 07:55	dregad	Status	assigned => feedback
2012-06-01 08:11	Nagendra Surya	Note Added: 0031957
2012-06-01 08:11	Nagendra Surya	Status	feedback => assigned
2012-06-01 08:21	dregad	Note Added: 0031958
2012-06-01 08:33	Nagendra Surya	File Added: Capture.PNG
2012-06-01 08:34	Nagendra Surya	Note Added: 0031959
2012-06-01 08:41	dregad	File Added: Screenshot from 2012-06-01 14:39:50.png
2012-06-01 08:43	dregad	Note Added: 0031960
2012-06-01 08:59	Nagendra Surya	Note Added: 0031961
2012-06-01 09:25	dregad	Note Added: 0031962
2012-06-04 17:41	dregad	Status	assigned => resolved
2012-06-04 17:41	dregad	Resolution	reopened => no change required
2012-06-16 06:34	atrol	Status	resolved => closed

Relationships