You can display various entities as cards on views. Some entities can be displayed together on the same view if they have common properties (such as Bugs, Tasks, User Stories).
| Entity | Card | Description |
|---|---|---|
| Epic | A high level work item that contains several Features. | |
| Feature | A high level work item that contains several User Stories. It can't be assigned to an Iteration, but is useful for release planning and roadmapping. | |
| User Story | A typical requirement. Example: "As a Human, I want to survive in a forest". User Stories can be assigned to a Release or an Iteration. User Stories can contain several Tasks and/or Bugs. | |
| Task | The smallest planning unit. A Task cannot be created without a parent 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 | A blocker — something that is blocking work on a User Story, Feature, Task or Bug. | |
| Release | A deliverable piece of software. Portfolios (Projects) can be split into Releases, and Releases can be split into Iterations. Releases have start and end dates. | |
| Iteration | Iterations must be created inside a Release. | |
| Team Iteration | Team Iterations relate to a Team and can include User Stories from several Portfolios (Projects). | |
| Test Case | A Test. A 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. | |
| Portfolio (Project) | Groups work (Features, Stories, Bugs) together. | |
| Program | High level item that groups Portfolio (Project) together. | |
| Team | Group of people that can work on several portfolios (projects). | |
| User | A person who has 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.
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.