ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Option to automatically watch things I've interacted with (Feature #738)
Description
I often find that I'd like to automatically watch thins I've "interacted" with, interaction being either that I've been assigned to it, that I've responded to a thread, and so on. Some parts of ChiliProject do that automatically (e.g. forums) without an option to deactivate it, while other don't do that (issues, wiki, news, …) but don't offer an option to activate that.
A first iteration could have a setting for all modules, while we could make it more fine-grained by providing a means to activate it for certain modules only.
Related issues
| related to Feature #193: Make issue reporter watcher of the issue | Open | 2011-02-14 |
History
Updated by Eric Davis at 2011-12-02 12:28 am
I like the idea but I'd like to see how it would be implemented. I want to keep the configuration for each user as simple as possible, we already have way too many buttons and dials in my opinion.
This is also related to what you proposed in #193. In fact, #193 might be a subset of this issue since reporting an issue is a type of interaction.
Updated by Felix Schäfer at 2011-12-02 06:16 am
Eric Davis wrote:
This is also related to what you proposed in #193. In fact, #193 might be a subset of this issue since reporting an issue is a type of interaction.
It is indeed.
I like the idea but I'd like to see how it would be implemented. I want to keep the configuration for each user as simple as possible, we already have way too many buttons and dials in my opinion.
I think ideally it would replace/supersede the current config with some of the same options: Auto-watch everything, things I interact with, only things I create, nothing. That could be refined per-module (e.g.: everything I interact with on forums, but just when I'm assigned the issue on issues) (the modules could provide a settings partial themselves), and I think the project-specific settings/overrides should go into the projects instead of having everything crammed in one view (that's probably a separate issue though).