MantisBT - TestLink
View Issue Details
0002343TestLinkCustom fieldspublic2009-04-07 06:392010-05-01 20:34
1.9 Beta 2 
IE7, FireFox
0002343: CF_ESTIMATED_EXEC_TIME does not get displaid
Estimated execution time, which is a useful feature, can not be displaid unless during defining the custom fiel you set both "display" and "enable" to YES. As I understood, it could be displaid without giving permission to modify it..
Please look at the attached file, which is the setting I used
No tags attached.
related to 0002525closed fman No "CF_ESTIMATED_EXEC_TIME" in test report 
jpg Custom-field-issue.jpg (42,387) 2009-04-07 06:39

jpg Unassigned_CF_Cant_be_deleted[2].jpg (76,920) 2009-04-08 22:58
Issue History
2009-04-07 06:39aostadNew Issue
2009-04-07 06:39aostadFile Added: Custom-field-issue.jpg
2009-04-07 06:39aostadBrowser => IE7, FireFox
2009-04-07 06:39aostadPHP Version => 5
2009-04-07 21:07mhavlatSeveritymajor => tweak
2009-04-08 05:03aostadNote Added: 0006256
2009-04-08 16:17fmanNote Added: 0006266
2009-04-08 16:18fmanStatusnew => feedback
2009-04-08 22:52aostadNote Added: 0006298
2009-04-08 22:58aostadFile Added: Unassigned_CF_Cant_be_deleted[2].jpg
2009-04-08 22:59aostadNote Added: 0006299
2009-04-09 00:35fmanNote Added: 0006301
2009-04-09 05:57aostadNote Added: 0006302
2009-04-09 14:49fmanNote Added: 0006304
2009-04-09 15:19fmanStatusfeedback => assigned
2009-04-09 15:19fmanAssigned To => fman
2009-05-21 09:55mhavlatRelationship addedrelated to 0002525
2010-01-21 01:26fmanStatusassigned => resolved
2010-01-21 01:26fmanFixed in Version => 1.9 (DEV)
2010-01-21 01:26fmanResolutionopen => fixed
2010-05-01 20:34fmanStatusresolved => closed

2009-04-08 05:03   
This problem shows up in both CF_EXEC_TIME and CF_ESTIMATED_EXEC_TIME. BTW, I forgot to say that I select "script" for the type of custom field.
2009-04-08 16:17   
why script type ?
this fields has to be numeric.

look on your installation (third_party\user_contribution\) for sql script that creates this field in right way.

more: please give detailed steps to reproduce
2009-04-08 22:52   
Regardless of the type, the feature should either work properly or send a message that it can not handle it. Actually, it is a good test for the feature.

I rename the CF_ESTIMATED_EXEC_TIME to badCF_ESTIMATED_EXEC_TIME and created another one. The reason that I rename it is that I could not delete it even after unassigning the custom fileld and removing all test cases and test suites (I have raised another issue for it). Then I created another one with type "numeric". The result is the same. the custom field can't be displaid unless you make it enable too, which is not what I want. It should not be editable for tester in specification or execution page.

To Reproduce just follow regular steps:
1. As admin navigate to Home-->Define Custome Fields
2. Click on "Create"
3. Fill empty filed as below:
   -Label :Estimated Exe. Time
   -Display on test specification: Yes
   -Enable on test specification: No
   -Display on test execution: Yes
   -Enable on test execution: No
   -Display on test plan design: Yes
   -Enable on test plan design: Yes
4. Click on "Update" to create it
5. Navigate to Home-->Assign custom fields
6. check-mark the custom field and click on "Assign"
7. As "leader", generate test cases from requirement documents
8. Navigate to Home-->Add/Remove Test cases and add test cases to your test plan and save it. You should be able to observe the custom field after adding test cases in your test plan.
9. Go to Execution page and select a test case
10. it is expected to see the custom field for the test case (Id does not show up)
11. Go to Spewcification and select a test case then click on Edit to see if there is the custom field for the test case. (It does not show up).

NOTE: During defining the custom field, if you set "Enable" for test execution and specification then you can see the custom field. But the field would be ditable which is not what we want.
2009-04-08 22:59   
The uploaded file is a screenshot I got for issue 2353 (an unassigned CF can not be deleted, however, it shows what I explained in my reply.
2009-04-09 00:35   
>> It should not be editable for tester in specification or execution page.

custom field rights to read/write are not as advanced as in mantis, their are not managed using roles, then if is editable it is for everyone.

If you want a different thing => open a new issue.
2009-04-09 05:57   
Based on user manual, there is a differenec between "Enable" and "Display" option in configuring a Custom Field. If there is no difference why there are choices for Displaying and Enabling.
2009-04-09 14:49   
I will retest and then, we will return on your sentences that IMHO are far from constructive.