Reports: Remove unused cols #13579
Merged
Reports: Remove unused cols #13579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Checked commits kbrock/manageiq@13f10b9~...308c0e2 with ruby 2.2.6, rubocop 0.46.0, and haml-lint 0.19.0 |
|
@dclarizio @martinpovolny please move |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
col_orderandHeaderdefine which fields are displayed in the ui.colsdefines which fields are brought back from the database.This PR removes the columns that are not displayed
Other reports bring back
nameorupdated_at/created_atbut don't display them.product/views/Condition.yamlbrings back a number of columns, but only displaysdescriptionI'm questioning whether it is even used.Please let me know if I've misunderstood the fields in reports.
https://www.pivotaltracker.com/story/show/137377399