After upgrading from 1.9.3 to 1.9.4, the default ordering of newly created Requirements within a Req Spec as shown in the Navigator has changed from oldest -> newest to newest -> oldest. Is there a configuration setting to set this ordering back to what it was in 1.9.3? I looked at $tlCfg->gui->tprojects_combo_order_by, but this is not a "combobox".
We number our Requirements with a convention: APP001, APP002, etc., so it's more natural in our cases to see them ordered APP001, APP002 instead of the other way around.
Or is this a bug? I can create a bug for it, but not if it's something that can be changed through configuration.
Default ordering of Requirement within Spec in 1.9.4
Moderators: Amaradana, TurboPT, TL Developers
-
- TestLink user
- Posts: 12
- Joined: Sun Aug 15, 2010 2:08 am
Re: Default ordering of Requirement within Spec in 1.9.4
if order has been changed ( I'm not sure) in anycase Dev Team, will not consider this is a bug.
If you want open a feature request to make order configurable.
It will be great if you also provide the code to implement this feature
If you want open a feature request to make order configurable.
It will be great if you also provide the code to implement this feature