History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: QB-2356
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Steve Luo
Reporter: J. Mash
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

Changes Filtering Functionality

Created: 06/Mar/15 07:20 AM   Updated: 16/Jan/16 03:56 AM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown

 Description  « Hide
This is a request to add functionality to allow filtering the list of changes that appears in the build overview by at least the following criteria:

    - description
    - user

This would be distinctly different than detecting changes as a build condition, which still includes the changes in the overview, even if a build wasn't triggered by them.

 All   Comments   Work Log   Change History      Sort Order:
Steve Luo [07/Mar/15 01:37 AM]
Changes in the build overview only shows latest 10 commits and an overview scorecard, if you want to filter the list, you need go to SCM changes tab, not in build overview.

J. Mash [11/Mar/15 04:49 PM]
This request is more from an administrative point of view, rather than the users point of view.

The issue is that, there are some administrative / automation accounts that generate changes in the repository that shouldn't be displayed, to anyone, ever. Those changes are generated during the current build, but won't show up in the overview (or SCM Changes tab) until the next build. Then what happens is all you see in the overview is a huge list of changes from the automation user and none of the valid ones from the developers.

What I'm talking about is having a way to say:

  - Don't display changes from this user, ever.
  - Don't display changes with a description starting with <string>, ever.

Thinking about it a bit more, what might be more ideal is to just turn the 'overview' into a script where the default is to just blindly display the last 10 results, but that I could override to provide different functionality. The script could be given the complete list of changes associated with the build (everything from the SCM Changes tab), and then I would prune that list in whatever ways I wanted, and then return the pruned list to be displayed in the overview.

That would also allow for decreasing/increasing the number of results in the overview, if desired.

Robin Shen [16/Jan/16 03:56 AM]
We can accept contribution of this feature.