Bug 882903 - The admin tag "featured" was not visible in the app creation page.
Summary: The admin tag "featured" was not visible in the app creation page.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-03 10:10 UTC by Mengjiao Gao
Modified: 2015-05-15 01:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-05 23:17:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
No tag "featured ' shown in the app creation page. (156.88 KB, image/png)
2012-12-03 10:10 UTC, Mengjiao Gao
no flags Details

Description Mengjiao Gao 2012-12-03 10:10:17 UTC
Created attachment 656519 [details]
No tag "featured ' shown in the app creation page.

Description of problem:

When I tested on devenv_2547, I found the admin tag "featured" was not visible in the app creation page: /app/console/application_types.
I have tried to add this tag to my quickstart app, but the tag was not visible in the tag list of the app in the app creation page as the attachment shown.

Version-Release number of selected component (if applicable):
devenv_2547

How reproducible:
always

Steps to Reproduce:
1.Add a quickstart app named "spring" using admin account, according to the steps described in US3046, and add admin tags "new","premium", and "featured" to the quickstart app .
2.Hit /community/cron.php in the browser. 
3.Go to the website, check the tags shown in the app creation page of "spring".

Actual results:
At step 3, admin tag "featured" was not visible in the app creation page

Expected results:
At step 3, this tags should be shown in this page.

Additional info:

Comment 1 Clayton Coleman 2012-12-05 23:17:03 UTC
Intentional, featured puts them in the top, but doesn't show up elsewhere.


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