ServiceNow Best Practices on When to Create a Story vs CWMTASK?

[Marlon Dale]

Exploring CWM I was wondering if there was any official documentation on use cases of when it is appropriate to create a story vs create a cwmtask when creating work items in CWM.

[Sunil B N]

Hi @Alpa82 ,

Its stored in sn_cwm_task which references the respective story. We understand that there is no direct field on story as of now. 
sn_cwm_sprint stores all the sprints which you can filter by Board.
Thanks and regards,
Sunil B N

[Alpa82]

Thank you @Sunil B N .

As you can understand, the user experience might be confusing.
As if I view story in CWM and it has field Sprint populated then when the same record is opened in the full view directly from CWM, the Sprint field is empty and references to different table..

Is this something that will be improved in any upcoming version, as the user experience is inconsistent in CWM?

When story opened in full view directly from CWM

Additionally, is the sn_cwm_task, with type=Story created for each rm_story record,  that is added or planned in the CWM? What is the connection between the rm_story and at the sn_cwm_task, type=story?

If there is a need to build the report on stories,  the report be built on the sn_cwm_task or rm_stories?
Is there some data model, that you could share which would show the connection between the different tables involved in the CWM process ?

Thank you very much

[Sunil B N]

Hi @Alpa82 ,

I completely agree with you that if both Agile 2.0 and CWM sprints are in use for the same story it can be confusing to the end user.
a. Is this something that will be improved in any upcoming version, as the user experience is inconsistent in CWM?
We will definitely have more guidance on this in the future.

b. Additionally, is the sn_cwm_task, with type=Story created for each rm_story record,  that is added or planned in the CWM? What is the connection between the rm_story and at the sn_cwm_task, type=story?

Yes, we create a rm_story record and create a shadow task to bind it the board through sn_cwm_task. We reference rm_stroy through task field on the sn_cwm_task.

Each CWM Board(sn_cwm_board) can have TASKs(sn_cwm_task). Each TASK(sn_cwm_task) can exist as stand alone or refer to existing task(or task extensions like story/incident/so on) record in ServiceNow.

c. If there is a need to build the report on stories,  the report be built on the sn_cwm_task or rm_stories?
Ideally it would depend upon the business use case. Everything potentially can be built on sn_cwm_task table for OOTB common fields. for other task types you can dot walk on task reference. We have plans to build OOTB reporting in 2026

d. Is there some data model, that you could share which would show the connection between the different tables involved in the CWM process ?

We have multiple tables, and the model may evolve as new features are introduced

I have attached the model for reference only.

Thank you for raising these important questions. Please keep them coming—we’re happy to help.

Best Regards,
Sunil B N

[Sunil B N]

Hi @Alpa82 
CWM Sprint info is store on sn_cwm_task as Sprints are encapsulated at Board level.
Sprint table for CWM - sn_cwm_sprint. 
sn_cwm_task will have all stories reference and sprint to which they are tied to within CWM.

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