Project Requirements Related List Functionality

[Jim Hughes1]

The Related List  for Requirements Functionality is very basic.  The documentation is marginal at best. There are three fields for a users to be assigned, Source, Owner, and Assigned to.  

How are other companies defining and using each of the Users Name Fields?   Source> Person who provides the Requirements?   Owner> Person that is responsible for the requirements? Assigned to> person who is responsible to capture the requirements?

Can these requirements be mapped to  test module?

[Ankur Bawiskar · Accepted solution]

@Jim Hughes 

This related to demand management

Following is the interpretation as per the docs and analysis

https://docs.servicenow.com/bundle/orlando-it-business-management/page/product/planning-and-policy/c...

Source	User requesting the requirement. This field is automatically populated with the name of the person filling out the form, but the source could be a different person who identified the requirement.
Owner	User or group who is responsible for managing the requirement or making sure that the requirement is met.

Assigned to auto-populated with the logged in user who has raised the requirement

This is handled via the dictionary override on assigned_to task field

Mark ✅ Correct if this solves your issue and also mark 👍 Helpful if you find my response worthy based on the impact.
Thanks
Ankur

[MrMuhammad]

HI @Jim Hughes,

Source field -  Populated by the user who is requesting the requirements. It has dynamic default value which sets source field to logged in user. 

Owner - Documentation around this, is not correct. This field is referenced from Users [sys_user] and it holds the users NOT group that is responsible for managing and overlooking the requirements. This field again has a dynamic filter which sets owner to logged in user OOB.

Assigned to - This is the person working on gathering requirements and OOB again the default value is set to logged in user.

Regarding the relationships/mapping with TEST module, OOB we have TESTING TASKS relatedlists available but hidden on Requirements form based on different criterias i.e. All the testing tasks associated with current requirement, Testing task where start date derived from current requirement etc. 

You can right click on header or click on hamburger icon on header top left and select configure > relatedlist.

Add all the Testing Task relatedlists and see which on helps you achieve your goal. 

Please let me know if this helps & mark my response as ACCEPTED & HELPFUL if it answered your question.

Thanks & Regards,
Sharjeel