Start date /end date functionality in CWM board

[Shakara Whitehe]

I've run into a few issues when adding Stories to the CWM task board. The biggest one is that the Start and End Date fields don't populate in the list view and aren't editable. From what I can tell, rm_story and sn_cwm_task use different fields for these values, so they don't seem to map correctly.

I also noticed that while you can update the dates from the sn_cwm_board record, other changes (like the Short Description) aren't reflected in the CWM list view. It's not clear to me how fields are synced between the Story and sn_cwm_task records. On top of that, Start and End Dates can't be edited from the Gantt view for Stories.

This all seems to be OOTB behavior, but it feels pretty limiting. Has anyone found a workaround or a better approach?

[Sunil B N]

Hi Ron,

Thanks for the further details.
Issue 1 - 
Users can track same work in different Boards (which is absolutely valid). This will not be problem until they are added to two different sprints. In the coming release we have added warning to show when same stories are dropped into different sprints of different Board. 

Issue 2 - Absolutely you are right. We will address it at the earliest next release.

Thanks for bringing these issues to light. This kind of feedback helps us build something that actually works the way teams need it to.

Best regards,
Sunil B N

[ajmalmuhamm]

This appears to be the expected out-of-the-box behavior. Although Stories (rm_story) can be displayed on a CWM board, they aren't fully synchronized with the corresponding sn_cwm_task record.

The CWM board primarily operates on sn_cwm_task, while Stories maintain their own fields (including Start/End Date). Since these fields don't have a direct OOTB mapping, changes made on one record aren't automatically reflected on the other unless there's explicit synchronization logic.

A few things you can check:

• Review any OOTB Business Rules, Flows, or Script Includes that create and maintain the relationship between rm_story and sn_cwm_task.
• Verify whether the board configuration exposes mapped fields or if only specific fields are synchronized.
• If Start and End Dates are a key requirement, you may need to implement a custom Business Rule or Flow to keep the fields in sync between the two tables.
• For Gantt editing, if the board is reading from sn_cwm_task while the source of truth is rm_story, the dates won't update unless synchronization is implemented.

If you've confirmed there is no OOTB synchronization for these fields, then this is likely a product limitation rather than a configuration issue. A custom synchronization mechanism (Business Rule, Flow Designer, or Script Action) is the typical workaround until ServiceNow provides native support.

[Sunil B N]

Hi @Shakara Whitehe 

The fields of the original record are intentionally kept on the original record and not copied to make them editable on the CWM task. (Apart from custom fields and few agile columns for tracking purposes)

Reasoning: This applies to all connected work items that reference the original record. We preserve the security model and field permissions as intended from the source record (the Story in this case). That's why you don't see Short Description and other Story fields directly on the CWM task (or in platform list of CWM task).

To edit these fields, use the side panel or open the full details view of the Story record itself. This keeps field governance intact and ensures changes respect the original record's permission structure.

Please let me know if you have any questions further.
Best Regards,
Sunil B N