Why are there 2 sprint fields when creating a story?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
If I'm not mistaken CWM Sprint references sn_cwm_sprint and Sprint references rm_sprint
My question is for a UX perspective why are both shown and is it the intended use of CWM for net new items to use/show both sprint fields.
It also seems the CWM Sprint field pulls ALL sprints in the table while the Sprint field seems to filter to only display sprints from the current board. Is this expected and will there eventually be a similar filter on the CWM Sprint field to only pull sprints from the same board or space?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Marlon Dale
Whilst I can’t provide an official answer, my assumption is because ServiceNow have deprecated Agile Development 2.0, users migrating to CWM need to be able to use their stories from Agile 2.0 without having to move their data across. Helps make the transition a lot smoother!
I presume that down the line, once Agile 2.0 is completely unsupported, they’ll remove it.
Hope this helps! If you found it useful, feel free to leave a 👍 Kudos. If it answered your question, accepting it as a solution helps others find the answer too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @Marlon Dale ,
Why we have two sprint fields- One points to rm_sprint (legacy) and another points to new sprint table sn_cwm_sprint.
If you would like to use only cwm sprint, you can modify form view to hide rm_sprint so that its not confusing for users.
We didn't want to hide automatically as each organisation would have their own strategy for moving from Agile 2.0.
Why are we seeing the Sprints of other Boards in sprint field?
This is a bug which we have recognised already, we will be fixing in the upcoming release.
Let me know if you have any further questions.
Best Regards,
Sunil B N
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Same question but for the Epic field from Agile and the new Scrum Epic table. In the context of wanting to move out of Agile 2.0 completely what is the servicenow best practice recommended usage of the 2 Epic fields in the Story when interacting with net new stories and epics in CWM?