Key: |
QB-3029
|
Type: |
Improvement
|
Status: |
Open
|
Priority: |
Major
|
Assignee: |
Steve Luo
|
Reporter: |
J. Mash
|
Votes: |
0
|
Watchers: |
0
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 10/Aug/17 04:13 AM
Updated: 19/Jan/18 03:05 AM
|
|
Component/s: |
None
|
Affects Version/s: |
None
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
File Attachments:
|
None
|
Image Attachments:
|
|
|
This is an improvement request to modify the SCM Changes page such that it will always display a specific subset of information about a change, regardless of how many file modifications it contains.
|
Description
|
This is an improvement request to modify the SCM Changes page such that it will always display a specific subset of information about a change, regardless of how many file modifications it contains. |
Show » |
|
The number of changes and file adds/edits/removes are displayed as question marks and are greyed out (non-interactive) to indicate that this feature is not available for this particular change set. The goal here is to ensure that some amount of information is available for every single change that went into the build, even in cases where there may be too many file modifications to display without crippling the server.
There are a couple reasons why this is extremely important to us:
- We have a number of clients that use the SCM Changes page to determine which build a feature that they've requested has become available.
- We use the SCM Changes page to generate (and export) a comprehensive list of changes/change descriptions between our previous release build and the current one, which may span a couple dozen release-candidate builds.
These things don't work quite as well when some changes aren't displayed (either because the change set has too many file modifications or was unlucky enough to have been processed after one that did).