Team-Based Notifications for different Task Type Assignments

[Mustameer_Khan]

What’s New?

Until now, notifications in SAP Cloud ALM were primarily driven by direct task assignments to individual users. With this new enhancement, when a team is assigned to a specific task type, a notification is automatically sent to all members of that team. This eliminates the need for assigning tasks individually while ensuring all relevant team members stay informed and engaged.

 

How it works? 

When a project lead/member assigns a team to a task , the system now sends a notification to each member of that team. Users receiving the notification can directly navigate to the associated task in context, making it easier to start collaborating or taking action immediately. This feature supports a more scalable and streamlined way of task delegation, especially in projects with large or cross-functional teams.

Real-World Example : 

Let’s say your project has two teams:

• Team A: responsible for Testing tasks

• Team B: responsible for Development tasks

Scenario:

• A Testing task(project task) is created in the system.

• The project manager assigns Team A to this task.

• Result: All members of Team A receive a notification, and each of them can click on the notification to jump straight into the Testing task and begin their work.

If a user belongs to Team B only, they will not receive any notification, since their team was not assigned to the Testing task . This ensures targeted communication and minimizes notification noise.

Supported Task Types

This new functionality is available across most major task types in SAP Cloud ALM. Specifically, team-based notifications on task type assignment currently support:

• Roadmap Tasks

• User Stories

• Requirements

• Project Tasks

• Sub-tasks

• Defects

Exceptions:
This feature is not currently supported for: Quality Gates , Checklists

 

New Notification Types Introduced

To support this team-based assignment model, SAP Cloud ALM now includes dedicated notification types that trigger when your team is assigned to certain task types. The following new notification types are available: 

• Tasks: assigned to your team

• Requirements: assigned to your team

• Defects: assigned to your team

These ensure that notifications are not only timely but also clearly categorized by content type, so users immediately understand what they’re being asked to engage with.

Additional Safeguards in Place : What Happens When Changing the Assigned Team?

As part of this enhancement, we've also introduced a built-in safeguard to ensure that changes in team assignments are not inconsistent if there is already a Responsible member assigned to the Task. Here’s how we handle this scenario:

Scenario
Let’s say:

• Your project has multiple teams

• Different users are assigned to different teams

• You have a task assigned to User A

• User A is not part of Team X

Now, you decide to change the team assignment of the task to Team X.

 What happens next?

• The system will warn you that User A will be removed as the responsible person for the task, since they are not part of the newly assigned team.

• You will be given a choice, based on effort and context:

  • If feasible, you can choose to keep User A assigned to the task.

  • Alternatively, if keeping them is not supported in that context, you can simply cancel the team change to avoid losing the individual assignment.

Summary : Why This Matters

• Efficiency: Assigning at the team level reduces manual overhead and ensures consistency across similar tasks.

• Clarity: Only relevant users receive notifications, which avoids confusion and overload.

• Contextual Awareness: Users can navigate directly to the task type context, without hunting through the system.