|Anonymous | Login | Signup for a new account||2018-12-15 12:31 UTC|
|Main | My View | View Issues | Change Log | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005524||TestLink||General||public||2013-02-12 09:01||2013-05-26 18:50|
|Platform||OS||Windows||OS Version||XP Pro 2002 SP3|
|Product Version||1.9.4 (2012 Q3 - bug fixing)|
|Fixed in Version||1.9.6 (2013 Q1 - bug fixing)|
|Summary||0005524: Creating build using test case user assignment from existing build. Newest build is not selected by default.|
|Description||when i try to create a build and use test case/user assignment from an existing build the newest build is not selected by default.|
In my case always the second entry in the select list is selected by default.
|Steps To Reproduce||1.Enter Builds/Releases from the main window|
2.Create a build
3.Check the "Copy tester assignments"- checkbox
4.The newest build should not be selected
To see this effect you must have at least 3 builds already created.
|Additional Information||I tried to debug your code and it looks like the issue comes from |
init_source_build_selector() in buildEdit.php.
594: // if no build has been chosen yet, select the newest build by
595: if( !$argsObj->source_build_id )
597: $htmlMenu['selected'] = key($htmlMenu['items']);
It seems that the key()-function in line 597 returns always the same value.
|Tags||TO BE FIXED on 2.0|
|Browser||Firefox 18.0.2 , IE 8.0|
|QA Team - Task Workflow Status||READY FOR TESTING|
|Attached Files|| testlink194org.zip [^] (59,929 bytes) 2013-02-12 09:01|
testlinkIssue.JPG [^] (68,304 bytes) 2013-02-12 09:02
|For better understanding you could look at the screenshot i have uploaded|
edited on: 2013-02-12 11:12
IMHO is not an issue, any guess the system can do has same value.
I do not think you always want to do is a copy of previous build.
key() returns the first key on the item set.
If you want to have a quick fix, You need to check the order used to get the build set.
If order is done DESC by build ID, I suppose the current implementation can do the requested action
in fact we almost every time copy from the newest previous build.
at moment i am a little bit confused, because the comment in init_source_build_selector() says, that the newestes build will be selected.
Could you tell me where i can change the order of the build set?
I guess it must be somewhere in the config.php but i couldn't find it.
For my case i replaced
In this way the newest build is selected as default
Part of issue origin was not using reset($htmlMenu['items']).
With reset(), combo will be created ordered by name ASC.
Change has been done to request order by id DESC on get_builds_for_html_options()
|2013-02-12 09:01||theflasher||New Issue|
|2013-02-12 09:01||theflasher||File Added: testlink194org.zip|
|2013-02-12 09:02||theflasher||File Added: testlinkIssue.JPG|
|2013-02-12 09:03||theflasher||Note Added: 0018312|
|2013-02-12 11:06||fman||Description Updated||View Revisions|
|2013-02-12 11:08||fman||Note Added: 0018313|
|2013-02-12 11:12||fman||Note Edited: 0018313||View Revisions|
|2013-02-13 09:00||theflasher||Note Added: 0018319|
|2013-02-16 14:47||fman||Note Added: 0018335|
|2013-02-16 14:49||fman||Summary||Issue while creating build from existing build. Newest build is not selected by default. => Creating build using test case user assignment from existing build. Newest build is not selected by default.|
|2013-02-16 14:49||fman||Description Updated||View Revisions|
|2013-02-16 14:52||fman||Tag Attached: TO BE FIXED on 2.0|
|2013-02-16 14:53||fman||QA Team - Task Workflow Status||TBD => READY FOR TESTING|
|2013-02-16 14:53||fman||Note Added: 0018336|
|2013-02-16 14:53||fman||Status||new => resolved|
|2013-02-16 14:53||fman||Fixed in Version||=> 1.9.6 (2013 Q1 - bug fixing)|
|2013-02-16 14:53||fman||Resolution||open => fixed|
|2013-02-16 14:53||fman||Assigned To||=> fman|
|2013-02-16 14:53||fman||Relationship added||child of 0005406|
|2013-05-26 18:50||fman||Status||resolved => closed|
|Copyright © 2000 - 2018 MantisBT Team|