- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2 hours ago - edited an hour ago
Problem
When custom state choices are used as columns on the Enterprise Agile Planning (EAP) Planning Board, cards appear in the column when moved but disappear after a page reload.
Cause
On page reload, the Planning Board does not determine column placement from the record's state value alone. Instead, it maps cards to columns based on state buckets configured in the dictionary for the state field on the rm_story table.
If a custom state choice is not added to the appropriate state bucket in the dictionary, the Planning Board cannot map cards to that column after reload.
Behavior when state bucket is not configured
You may observe the following sequence:
· Cards can be dragged into a column representing the custom state.
· The state change appears to work and the card is visible initially.
· After refreshing the Planning Board, the cards no longer appear in that column.
This is expected behavior when the custom state is not mapped in the state bucket configuration.
Resolution
Creating a custom state choice alone is not sufficient for it to work correctly on the Planning Board. You must also add the custom state to the appropriate state bucket through the dictionary configuration for the rm_story state field.
Procedure:
1. Navigate to System Definitions > Tables.
2. Search for the rm_story table and open its record.
3. From the Columns related list, locate the State column’s record and open it.
4. In the Dictionary Overrides related list of the State Dictionary Entry form, search for the rm_story table and open its record.
5. Update the Attributes field to include the new custom state choice in appropriate state bucket.
6. Save the changes.
Once the custom state is included in the appropriate state bucket, cards in that state persist correctly on the Planning Board, including page reloads.
Summary
Both of the following steps are required for custom states to work consistently on the Planning Board:
· Create the custom state choice.
· Add the custom state to the appropriate state bucket via the rm_story state field's dictionary configuration.
