Key: |
QB-912
|
Type: |
Improvement
|
Status: |
Resolved
|
Resolution: |
Fixed
|
Priority: |
Major
|
Assignee: |
Unassigned
|
Reporter: |
Don Ross
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
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.
|
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.
|
Show » |
No work has yet been logged on this issue.
|
|