| << Back to previous view |
|
[QB-912] Ability to re-order items on build options page for improved clarity to users
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.1.38 |
| Fix Version/s: | 5.1.0-rc4, 5.1.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Don Ross | Assigned To: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
To present a consistent and understandible interface to developers launching builds, it is helpful to order the items on the Build Options page in a logical fashion, with frequently-changed options near the top and more obscure options near the bottom, and related options grouped together.
Because the order of items on the page is based on the order of the matching variables on the Variables page, the options can be re-ordered by re-ordering the variables themselves; however, inherited variables are always dropped to the bottom of the page, and their order cannot be modified. As a result, these inherited values are forced to the bottom of the Build Options page as well. Since my most commonly-changed options are also the ones defined in my top-level configuration, the end result is maximum possible confusion for the developer. |
| Comments |
| Comment by Robin Shen [ 19/May/11 07:32 AM ] |
| Inherited variables are not defined in child configurations, hence their order can not be changed in child configurations. How about override the variables and then change the order from child configurations? |
| Comment by Don Ross [ 08/Jun/11 01:53 PM ] |
|
Then, if I change the definition at the top-level, I have to change it by hand in all the children as well.
I would expect the tool keep all variables in the same order in which they were defined in the top level, even if they get redefined. New variables added in child configurations would be problematic; I would like to see them inserted where I want them rather than automatically at the top, but I can see where that could be a challenge. Instead, you could force me to create a dummy variable at the top level to set the order, which I can then override in the child configuration(similar to a dummy step). I think, though, the best solution would be to make order of items on the build options page editable, ignoring the order of items in the Variables tab; that is where the problem is manifesting. |
| Comment by Robin Shen [ 20/Nov/13 02:16 AM ] |
| Variable prompt setting now have an order property controlling orders of prompted variables. |