- No Cards are displayed
- Cannot Prioritize Cards on a View
- Project and Team selection is reset
- Troubleshooting Performance Issues with On Demand Accounts
- Problem: Entities in work hierarchy are orphaned and belong to different scopes of work
- No Lanes are displayed
- Unable to use Global Search
Sometimes when you configure a new View, you’re not able to filter your Cards by some property. Or, you’re trying to select some property as a Lane (i.e. Row or Column) when you configure your Board but you cannot do that. Here are the most possible reasons why.
Some properties are Entity-specific so far. That is why you’re able to filter, sort, or distribute Entities by some property only when all the Entity Types selected in the View Setup do support the corresponding one.
To not be confused why some Entity-specific properties are not available for selection, please select some Property to represent Rows or Columns in advance when you creating a new View from scratch. The Setup dialog will suggest you what Card Types are compatible with the Lanes you've chosen. In addition, most frequently used setups are described below:
Feature field is available for User Stories only. So you can use the field as a lane when only User Stories are selected as cards in your View Setup. When you would like to see both User Stories and Tasks on your board and filter User Stories by Features, select User Stories as Lanes and Tasks as Cards. Then you’ll be able to filter out your Lanes (i.e. User Stories) by Features. Hover your mouse pointer in the bottom area of the lane and press an appearing green [+] button to quickly add a User Story as a child to the corresponding Feature.
Requirements practice should be enabled in the settings of the Process your Project is related to if you would like to support Features for high level requirements management.
2. User Story
User Story field is available for Tasks, Bugs, Test Cases only. Drag-n-drop Tasks and Bugs between User Stories using this Board is a good way to change the parent User Story for your entities quickly when you split your User Story in two.
Find a detailed description of the Estimation Board view set up in the dedicated article.
4. Priority / Business Value
Priority field representing Business Value in View Setup is available for Features, User Stories, Bugs, Requests or Test Cases only. Drag-n-drop method is a good way to change the Business value for the entities quickly.
Severity field is available for Bugs only. So you can use the field as a lane when only Bugs are selected as cards in your View Setup.
6. Iteration / Sprint
Iteration (or Sprint) field is available for User Stories, Tasks, Bugs and Test Plan Runs or Builds only. Drag-n-drop tasks between Iterations using this Board is a good way to plan your Iterations quickly.
Iterations practice should be enabled in the settings of the Process your Project is related to if you would like to support Iteration Planning using your Views.
Release field is available for Features, User Stories, Tasks, Bugs and Test Plan Runs or Iterations or Builds only. Drag-n-drop tasks (e.g. Features or User Stories) and Iterations between Releases is a good way to plan your Releases quickly.
Requirements practice should be enabled in the settings of the Process your Project is related to if you would like to support Release Planning for high level requirements management.
8. Team Iteration
Cross-project Team Iteration field is available for User Stories, Tasks, Bugs and Test Plan Runs only.
Custom Fields and Custom Values
The values of Dropdown Custom Fields only are available as the Lanes so far. You can setup the board with your Custom Values when all the Entities selected as Cards do have the Custom Field with the same name. In the picture above both Features and User Stories have the Dropdown Custom Field with name Start Year and equal predefined values.
A Project Portfolio board is another sample. Here Projects are selected as Cards and Dropdown Custom Field values are Lanes.
If you’re not able to select Custom Field values as Lanes, please check that:
- The Custom Field is of the Dropdown type;
- The Custom Field is added to the corresponding entity;
- The Custom Field is added in the settings of the Process your Project is related to;
- All the selected entities have the Custom Field with the same name and values list.
You cannot access entity-specific fields when different types of entities are displayed on the same view so far.
a sales representative
Get a live
Let one of our product specialists create your account
and shape Targetprocess for your company needs.