-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
HCC service onboarding
-
False
-
-
False
-
Unset
-
To Do
-
100% To Do, 0% In Progress, 0% Done
-
-
-
This epic will serve as a template
Description
- Problem statement: This assumption is based on the fact that this service does not previously exist in the Red Hat Hybrid Console Cloud and users need to be able to find the services through multiple ways, including but not limited to navigation, homepage, and etc.
- Don’t be intimidated by the amount of text and number of stories in the ticket. Your HCC friends are always here to help! Slack channel: #uxd-team-hybrid-console-ux
- Purpose of the guideline
- UXD and Product Management reps for an app should fill out a series of Jira tickets to communicate an app’s user experience needs to the Platform Experience’s Product Management and UXD team. Understanding what your app needs requires that you review the global apps, services & assistance that the Hybrid Cloud Console (console.rh.com) provides (this needs some updating, so take with a grain of salt).
It is meant specifically for those working with customer use cases, workflows, and UI design (typically, other UX designers and product managers).
- UXD and Product Management reps for an app should fill out a series of Jira tickets to communicate an app’s user experience needs to the Platform Experience’s Product Management and UXD team. Understanding what your app needs requires that you review the global apps, services & assistance that the Hybrid Cloud Console (console.rh.com) provides (this needs some updating, so take with a grain of salt).
We encourage you to set up a kick off meeting with Platform Experience PM + UXD before filling out the tickets!
Instructions
- Please read the following instructions below. Do NOT edit the templates. Please clone the entire epic and edit from there.
- How does HCC define a ‘service’ and a ‘bundle’?
- Simply put, a ‘service’ is a URL that a user can land on to do something in the console. Some services have multiple subpages while others just have one main page. A “bundle” is a group of services that are all in one left nav panel.
- Example: The ‘Settings’ bundle
- The left nav for ‘Settings has a single page called ‘Integrations’. That is a service
- Then there is a top level nav item called ‘Notifications’ - that’s a service with collateral pages because it holds several subpages that are navigable items.
- URL, browser tab, and breadcrumbs
- Page title: Use sentence
- Browser tab: Auto-generated based on the structure of your left nav [Current page title - Parent page (if applicable) | Bundle]
- URL:_/bundle/highest-level-parent/…/lowest-level-parent/page-title
- Breadcrumbs: Auto-generated based on the structure of your left nav [Bundle > Highest-level-parent >...> Lowest level parent > Current page]
- See an example
- Learn about these conventions
- Helpful resources
Template
- General information about your service(s)
- What tasks will your end users perform with your app?
- [Add your response here (links, mocks, text)]
- What tasks will your end users perform with your app?
-
- What problems does your app solve for your end user?
- [Add your response here]
- What problems does your app solve for your end user?
-
- Will your service(s) be incorporated into an existing bundle (RHEL, Ansible, OpenShift, etc.), or will we need to create a new one?
- [Add your response here (links, mockups, text)]
- Will your service(s) be incorporated into an existing bundle (RHEL, Ansible, OpenShift, etc.), or will we need to create a new one?
-
- Bundle/Service name
- [Add your response here]
- Bundle/Service name
-
- Bundle/Service description
- [Add your response here]
- Bundle/Service description
-
- Pages that will exist in your service
Page name | Very short summary (This will show up in search results and ‘Service’ dropdown) |
- Next step, if you have questions or any hesitation, feel free to reach out to HCC UX team to set up a initiation call. Or if you want to take a crack at it yourself, please scroll down and fill out the stories attached in this epic
Remember, we will always have your back!