Mantis Bugtracker 

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005397TestLinkRequirement Managementpublic2012-12-05 14:302012-12-05 18:14
Assigned Tofman 
PlatformOSWindow 7OS Version
Product Version1.9.4 (2012 Q3 - bug fixing) 
Fixed in Version1.9.5 (2012 Q4 - bug fixing) 
Summary0005397: "$g_field_size->requirement_title" defined in does not apply to edit/create a requirements (reqEdit.php)
DescriptionThe length allowed for req_title in reqEdit.php is not consistent with the value defined via the constant("$g_field_size->requirement_title") in the if you changed the value of "$g_field_size->requirement_title".
Steps To ReproduceBackground:

 We use the testlink for managing our projects, one of them requires a relevant long title for requirement about 120 -130 characters long, which is beyond the current maximum length (100). After searching the help and testlink, I tries to change this by following steps below:

1- Modified the length of the field "name" of "req_revisions", and the length of the field "name" of "nodes_hierarchy".

2- Changed the input dimension of requirement defined in the /testlink/gui/templates/input_dimensions.conf

3- Changed the constant value of "$g_field_size->requirement_title" in

I thought the length should be extended successfully, but I found the length allowed is still 100, after digging it up, I found "100" is used in "regEdit:init_args" (line 76) rather than reading the value from

I knew it is not really a common situation for others, but I think if you did provide a way to configure this length value, it should be consistent through the whole project.

Could there be another to achieve this rather than changing the value in and input_dimensions.conf, such as or custom.input_dimensions.conf?

Many thanks

Yikang Mao
TagsNo tags attached.
Database (MySQL,Postgres,etc)MySQL
PHP Version
QA Team - Task Workflow StatusREADY FOR TESTING
Attached Files

- Relationships

-  Notes
fman (administrator)
2012-12-05 18:11

for a config that has to be done ONCE the level of configuration provided is more than enough

- Issue History
Date Modified Username Field Change
2012-12-05 14:30 YikangMao New Issue
2012-12-05 18:04 fman Assigned To => fman
2012-12-05 18:04 fman Status new => assigned
2012-12-05 18:11 fman Note Added: 0017975
2012-12-05 18:14 fman Task Workflow Status TBD => READY FOR TESTING
2012-12-05 18:14 fman Status assigned => closed
2012-12-05 18:14 fman Resolution open => fixed
2012-12-05 18:14 fman Fixed in Version => 1.9.5 (2012 Q4 - bug fixing)

Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker