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.
Ability to assign issues to groups (Feature #427)
| Status: | Open | Start date: | 2011-05-25 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: |  Eric Davis |
% Done: | 0% |
| Category: | - | ||
| Target version: | - | ||
| Remote issue URL: | http://www.redmine.org/issues/2964 | Affected version: |
History
Updated by Eric Davis at 2011-05-27 03:31 pm
I'm the author of the original patch. There were a few things I wanted to improve with it, but I think we could add it to ChiliProject and improve them as we go. I've heard a lot of people asking for this feature.
I'll see about rebasing the patch into a pull request (was from 2009-12-29!)
- Assignee set to Eric Davis
Updated by Anton Lukashev at 2011-05-31 12:21 pm
It would be great! Many thanks, Eric.
Updated by Kevin Wheatley at 2012-02-28 10:03 am
I'd like to add my support to this request.
Updated by mcnair scott at 2012-06-09 11:07 pm
+1 this would be useful for sure.
Updated by Mathieu MARACHE at 2012-08-29 11:43 am
+1 We need this also for our issue validation process. i.e. A group of members have the authority to validate issues before they can be eligible for further investigation and resolution of the issue
Updated by Wiki Bit at 2012-09-07 12:58 pm
+1 here ... this would be ideal for dispatching groups