You can display various entities on views as cards. Some entities can be displayed together if they have common properties (Bugs, Tasks, User Stories), some not.
|Epic||High level work item that contains several Features.|
|Feature||High level work item that contains several User Stories. It can't be assigned to Iteration, but useful for release planning and roadmapping.|
|User Story||Usual requirement. Example: "As a Human, I want to survive in a forest". User Story can be assigned to Release or Iteration. User Story can contain several Tasks and Bugs.|
|Task||Smallest planning unit. Task can't be created without a User Story.|
|Bug||Defect. Can belong to a User Story. Can be assigned to Release or Iteration.|
|Request||Initial requirement from the end user. It is handy to communicate and refine this initial idea in Request, then you can create Feature, User Story or Bug from the Request.|
|Impediment||Blocker. Something that blocks User Story, Feature, Task or Bug.|
|Release||Deliverable piece of software. Project can be split to Releases and Release can be split to Iterations. Release has start and end dates.|
|Iteration||Iteration must be created inside a Release.|
|Team Iteration||Team Iteration relates to Team and can include User Stories from several projects.|
|Test Case||A Test. User Story contains several Test Cases.|
|Test Plan||Just a set of related Test Cases. A single Test Case can belong to several Test Plans.|
|Test Run||Execution of a Test Plan. There can be many executions of a single Test Plan that provide you with runs history.|
|Project||Groups work (Features, Stories, Bugs) together.|
|Program||High level item that groups Project together.|
|Team||Group of people that can work on several projects.|
|User||A person who has an access to TargetProcess.|
Customizing looks and size of cards in a View is possible with Customize Cards feature.
Highlighting cards on the Views using your own rules is available with Visual Encoding.