makeplane / makeplane/plane

[feature]: Subscriber settings for Projects and Modules

Open
#4,795 6 comments 1 reaction 2 assignees View on GitHub

@srinivaspendem is already working on this.

Since Jun 13, 2024.

✨feature
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

The ability to configure subscribers for projects and modules within the software. Subscribers will receive notifications about all new issues created within the project or specific modules.

This feature is similar to what is available in Jira and has proven to be incredibly convenient and beneficial in project management. Implementing such a feature in your software would greatly enhance its usability and provide a more comprehensive solution for managing projects and tasks.

Why should this be worked on?
Benefits
  1. Enhanced Communication: Ensuring that all relevant stakeholders are automatically informed about new issues without manual updates.
  2. Improved Collaboration: Facilitating better coordination among team members by keeping everyone in the loop.
  3. Increased Efficiency: Saving time and effort by automating the notification process.
Implementation
  1. Project Level: Allow users to assign subscribers to an entire project, ensuring they receive notifications about all new issues within that project.
  2. Module Level: Provide the option to assign subscribers to specific modules within a project. This is particularly useful for larger projects where team members may only need to be aware of issues related to their specific modules.

Thank you for considering this request. I am confident that this addition would be highly appreciated by all users. Please let me know if you need any further information or clarification.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.