BugZero | ServiceNow BugID PRB1474598 - The tsp_project_manager role cannot view the apply...

ServiceNow - Defect ID: PRB1474598

The tsp_project_manager role cannot view the apply_planned_task_creator UI Page breaking "Prject Task Creator" UI Action process

ServiceNow - Defect ID: PRB1474598

The tsp_project_manager role cannot view the apply_planned_task_creator UI Page breaking "Prject Task Creator" UI Action process

Last updated on September 4th, 2024

BugZero Risk Score
5.8 Medium

Overall: 5.8

Severity: 6.4

Community: 3.7

Lifecycle: 8.2

What is the BugZero Risk Score?

ServiceNow Integration

Learn more about where this data comes from

ServiceNow Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Priority: Sev3
Article Views: 2
Affected Component: Project Management
Views: 1

Description

The "tsp_project_manager" role contains the "project_manager" role instead of the "it_project_manager" role. The "project_manager" role has the "DO NOT USE" description prefix, and for example the "Project Task Creator" UI Action calls a UI Page with an ACL based role restriction of "it_project_user": /sys_security_acl.do?sys_id=8b90d4d55395d0100ca5ddeeff7b1261 It's also documented to require this role and not the "project_manager" role as contained by the "tsp_project_manager" role. Steps to Reproduce 1. Ensure Teamspace 1 plugin is enabled. 2. Open a project as a user with "tsp_project_manager" role. 3. Click the settings button on top right (burger icon) then select "Project task creator" Ui Action. See the pop-up shows "Security restrictions prevent access to this page".

Workaround

Change the roles for these ACLs to project_user: sys_security_acl_role_1ac058995395d0100ca5ddeeff7b1266 sys_security_acl_role_2701d89d5395d0100ca5ddeeff7b121c sys_security_acl_role_e43f04515395d0100ca5ddeeff7b12ff sys_security_acl_role_ef9010d95395d0100ca5ddeeff7b120a

Related Problem

PRB1474598

Change history

2024-09-04 Added: Paris Patch 1 Hot Fix 1, Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Relevant Products

Click on a version to see all relevant bugs

Affected versions:Paris Patch 1 Hot Fix 1, Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Affected versions:Paris Patch 1 Hot Fix 1, Rome Patch 1, Rome Patch 10 Hot Fix 2b, Rome Patch 10 Hot Fix 4b, Rome Patch 3, Rome Patch 7, Rome Patch 9a, Rome Patch 9b, San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Tokyo, Tokyo Patch 1, Tokyo Patch 1b, Tokyo Patch 3, Tokyo Patch 4a, Tokyo Patch 4b, Tokyo Patch 5, Tokyo Patch 6, Tokyo Patch 6 Hot Fix 1, Tokyo Patch 6 Hot Fix 2, Tokyo Patch 7, Tokyo Patch 7 Hot Fix 1, Tokyo Patch 7a, Tokyo Patch 7b, Tokyo Patch 8, Tokyo Patch 8 Hot Fix 1, Tokyo Patch 9, Tokyo Patch 9 Hot Fix 2, Tokyo Patch 9 Hot Fix 2a, Utah, Utah Patch 1, Utah Patch 1 Hot Fix 1, Utah Patch 1 Hot Fix 1a, Utah Patch 1 Hot Fix 1b, Utah Patch 2, Utah Patch 3, Utah Patch 3 Hot Fix 1, Utah Patch 4, Utah Patch 4 Hot Fix 2, Utah Patch 4 Hot Fix 2a, Utah Patch 4 Hot Fix 3, Utah Patch 5, Vancouver

Fixed versions: No known fixed versions

Top ServiceNow Defects

9.4Defect ID: PRB1954123
Instance access issues due to Mutual TLS (mTLS) enablement on Zurich instances
8.5Defect ID: PRB1871576
Data visualization can be accessed by anyone with URL to visualization designer
8.5Defect ID: PRB1611377
CMDB Baseline creation job causing app node out of memory when a CI has a huge number of records referencing it
8.5Defect ID: PRB1788540
AWS Events Driven discovery is overloading Default Semaphores.
8.5Defect ID: PRB1928008
Upgrade to Yokohama releases can hang for Haraka enabled instance because of contention on kagami query registrar