Column-Specific Configuration:

The Manage Subscribers feature can be enabled or customized for each column in the board.

When enabled, administrators can specify which email addresses should receive notifications when tasks are moved into that column.

Example Scenario:

Suppose you configure the Testing column to notify the QA lead (e.g., qa-lead@example.com) whenever a task is moved into this column.

When a task is moved to the Testing column, an email notification is automatically sent to the specified subscriber, containing a direct link to the task.

Modal Interface:

To configure the feature, administrators click the Manage Subscribers menu item for a specific column.

A modal window opens, allowing administrators to add or remove email addresses that should receive notifications.

Notification Content:

The email notification includes:

A brief description of the task.

A direct link to the task within GitScrum, enabling subscribers to click and view the task details immediately.

Access Column Settings:

Click on the column name or settings icon to access its configuration options.

Enable Manage Subscribers:

Select the Manage Subscribers menu item for the column.

Open Modal and Add Emails:

In the modal window, enter the email addresses of individuals who should receive notifications when tasks are moved into this column.

Save Changes:

Once configured, save the settings to apply the changes.

Improved Communication: Automatically notifies stakeholders about important updates, ensuring they are always in the loop without requiring manual follow-ups.

Enhanced Collaboration: Keeps external stakeholders or team members who are not directly logged into GitScrum informed about task progress.

Increased Transparency: Provides visibility into the workflow, helping stakeholders understand the status of tasks and projects.

Direct Access to Tasks: Subscribers receive a direct link to the task, making it easy for them to review details and provide feedback if needed.

Software Development

Scenario: In the Testing column, configure the feature to notify the QA lead (qa-lead@example.com) whenever a task is ready for testing.

Benefit: Ensures the QA lead is immediately aware of new tasks requiring their attention, improving response times and efficiency.

Marketing Campaigns

Scenario: Set the Review column to notify the marketing manager (marketing-manager@example.com) whenever content is ready for approval.

Benefit: Helps the manager stay informed about pending approvals and ensures timely reviews.

Event Planning

Scenario: Configure the Setup column to notify the event coordinator (event-coordinator@example.com) whenever logistics tasks are ready for execution.

Benefit: Ensures the coordinator is promptly informed about setup tasks, reducing delays and improving coordination.

Support Teams

Scenario: In the Resolution column, notify the customer support supervisor (support-supervisor@example.com) whenever a high-priority ticket is resolved.

Benefit: Enables the supervisor to verify resolutions and ensure customer satisfaction.

Limit Subscribers: Avoid adding too many email addresses to prevent overwhelming recipients with excessive notifications.

Prioritize Key Stakeholders: Focus on notifying individuals who need to be informed about specific stages of the workflow.

Regularly Update Subscribers List: Periodically review and update the list of subscribers to ensure it reflects current project requirements and stakeholder needs.

Communicate with Stakeholders: Inform subscribers about the purpose of the notifications and how they can use the provided links to access task details.

A software development team uses GitScrum to manage their workflow with the following columns: Todo , In Progress , Testing , and Done .

Testing Column: Configure the feature to notify the QA lead (qa-lead@example.com) whenever a task is moved to this column.

Done Column: Set the feature to notify the product owner (product-owner@example.com) whenever a task is completed.

When a developer moves a task to the Testing column, GitScrum sends an email notification to the QA lead, including a direct link to the task. Similarly, when the task reaches the Done column, the product owner receives an email notification with a link to review the completed task.