Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Scrum users missing on the Assigned To list selection on scrum tasks - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Scrum users missing on the Assigned To list selection on scrum tasks
KB0697381

Scrum users missing on the Assigned To list selection on scrum tasks


1087 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


In Agile Development, when creating a scrum task from a story, if the "Assignment group" on the task is different from it's parent story "Assignment group", not all group members are available to be selected as "Assigned to".

Release


Kingston Patch 8

Cause


This is the Out-Of-Box expected behavior.

The "Assigned To" field on the "rm_scrum_task" table has a dictionary override that is set to use the following reference qualifier:

javascript:'sys_idIN'+ScrumSecurityManager.getScrumTaskDotAssignedTo(current);

This reference qualifier is calling "getScrumTaskDotAssignedTo" function on the script include "ScrumSecurityManager". This process will eventually call "getStoryDotAssignedTo" that returns the group members of the parent story:

getStoryDotAssignedTo: function (recRmStory) {
	var arrMemberSysIds = [];
	
	// Case 0: if assignment group is populated, return all members of it
	if (!recRmStory.assignment_group.isNil()) {
		var members = new GlideRecord('sys_user_grmember');
		members.addQuery('group', recRmStory.getValue('assignment_group'));
		members.query();
		while (members.next()) {
			arrMemberSysIds.push(members.getValue('user'));
		}
		if (arrMemberSysIds.length > 0)
			return arrMemberSysIds;
	}
 
 

Resolution


Changing this behavior requires customization, either by extending the ScrumSecurityManager or by not using the reference qualifier. As an example, unchecking "Override reference qualifier" on the "assigned_to" dictionary override for the "rm_scrum_task" table will revert the behavior to the "task" table dictionary definition, meaning that all group members that have the "itil" role will be listed.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.