Commented Issue: Make automatic notifications for projects more flexible [76]

It would be nice if there was some more granular configuration on how notifications are configured for the project. Currently it's either all or nothing, this means that users, in some cases, are getting way too many notifications they are not interested in.

For example, on a given project send notifications to users depending on the category selected for the issue. For example all UI issues will go to the UI team and all DB issue will go to the DB team, ...

To make it even more flexible this should be fully configurable depending on multiple attributes. For example:
- send notification to user X if:
- issues is in category C1
- has priority P1
- is of type T1
- ....

Comments: I don't disagree with you view on extensibility, but I think some basic functionality should already be built into the system. So let's say the system provides the extensibility you suggest, then I'd say ALL options I suggested before should already be implemented on the default package. The features I suggested are pretty common in most scenarios so having this built into the project is what makes more sense. Then you can have as many layers of extensibility as you want, but some basic stuff must be already there.