when try to set up current sprint on story on the basis of assignment group not geting current sprin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi @sudarshan5
please refer to this:
10+ Tips for writing a quality community question
And then try to describe your requirement better, this is too vague...
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @sudarshan5 ,
This looks like an expected behavior in Agile 2.0. The Sprint field is tied to the Assignment Group, which means unless the group is set, the Sprint field may appear read-only or not populate as you expect.
I’ve seen similar cases Community question which may resolve your problem:
In below community post users mentioned that the Sprint field only becomes editable once the assignment group is populated.
https://www.servicenow.com/community/spm-forum/agile-2-0-assigning-stories-to-sprints/m-p/1046335
KB article Sprint and Assignment group is not auto-populated on creation of a story from Sprint , which explains why the sprint/assignment group isn’t automatically set in some cases.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827739&utm
If you’d like it to populate automatically based on the assignment group, you may need to add a custom business rule or client script to enforce that logic. Out-of-the-box, the platform does not auto-assign Sprint purely from the group.
Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.