Bug 1400535 - Content view version search returns no results for searching by version name
Summary: Content view version search returns no results for searching by version name
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.3.0
Hardware: x86_64
OS: Linux
low
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-01 13:00 UTC by Andrii Balakhtar
Modified: 2018-08-02 20:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 20:59:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Andrii Balakhtar 2016-12-01 13:00:25 UTC
Description of problem:
Searching on content view version page returns no results if you try to search by full content view version name, e.g. 'Version 1.0'

Version-Release number of selected component (if applicable):
Sat6.3 Beta Snap6

How reproducible:
Always

Steps to Reproduce:
1. Create content view, publish it's new version.
2. Navigate to Content view -> #name# -> Versions page, make sure you can see 'Version 1.0' present, type 'Version 1.0' into search field.
3.

Actual results:
Search returns no results

Expected results:
Search should return cvv 'Version 1.0'

Additional info:
If you try to search by query `version = 1.0` corresponding version will be found, so searching isn't completely broken there, it just refuses to find the version by its full name.

Comment 2 Justin Sherrill 2016-12-01 16:56:22 UTC
There is no name that actually includes "Version ".  Its just there for clarity and to the user a bigger link to click on (I think).  

I'll try to think how this could be made more clear.

Comment 3 Bryan Kearney 2018-08-02 20:59:02 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.