Feature #482
closedDefault assignee on each project
Added by Motohiro Takayama almost 17 years ago. Updated about 7 years ago.
90%
Description
It would nice to have a setting item to select default assignment for a new ticket,
Files
default_assignee.patch (2.88 KB) default_assignee.patch | Raffaello Pelagalli, 2010-06-24 18:21 | ||
482.patch (6.62 KB) 482.patch | Felix Schäfer, 2017-03-14 22:49 | ||
default_assignee.png (42.7 KB) default_assignee.png | Jean-Philippe Lang, 2017-07-21 21:16 |
Related issues
Updated by Curtis Stewart over 16 years ago
I just was asked if this feature was possible.
This would enhance the usage from a group of users, so if possible this should be set the the project or the tracker.
Updated by James Robertson over 15 years ago
I would like to vote for this feature, as would the people in these discussion topics I imagine:
http://www.redmine.org/boards/1/topics/3736
http://www.redmine.org/boards/1/topics/5470
Updated by Tim Aleinikoff over 15 years ago
I would like to see this feature in redmine.
Updated by Eric Davis over 15 years ago
- Category set to Issues
Good idea. I'm thinking this would have to be per project.
Updated by Douglas Campos over 15 years ago
I'm looking at this now....patch is comming soon
Updated by Zarooba Rozruba over 15 years ago
This would be great, I have been trying to set up categories in many of projects. Some users try to fill every field out, and categories have own assignment.
However, half of my projects lack categories, and for those that do, only half of users bother with categories.
Updated by Douglas Campos over 15 years ago
I will need some help at the position of the selector in settings screen. (Visual tips)
wip branch at http://github.com/qmx/redmine/tree/ticket-482
Updated by Adam Piotr Żochowski over 15 years ago
Hi Douglas,
I have tried your change, am not sure if I understand how it behaves, could be that I failed backporting it to 0.8.3.
What I did to get your change going¶
SQL: ranalter table projects add default_assignee_id int;
/app/models/project.rb: added linehas_one :default_assignee, :class_name => "Member"
/app/controllers/issue_controller.rb: added lines @issue.assigned_to_id = @project.default_assignee.user.id
@project.default_assignee
/app/views/_projects/_form.rhtml: added lines
<p> <% members = @project.members.find(:all, :include => [:role, :user]).sort %> <%= f.select :default_assignee_id, members.collect{|member| [member.name, member.user.id]}, {:include_blank => :none} %> </p>
This is your change as far as I can read it.
Recommended change¶
The major change I would do is your issue_controller.rb.
You have changed that issue opens with a assigned to being already picked. This is wrong, as now category based assigned to are ignored.
Instead, I would put the default assigned to through the /app/models/issue.rb where I would add secondary fallback, If still no assigned to, use default assigned to. This would then become something along the lines of:
def before_create # default assignment based on category if assigned_to.nil? && category && category.assigned_to self.assigned_to = category.assigned_to end ++ if assigned_to.nil? ++ self.assigned_to_id = @project.default_assignee_id ++ end end
(not sure if proper diff syntax, hand made)
question¶
In model project.rb, you have defined that default_assignee is a member type, yet in database, and everywhere else, you write user.id (not member.id) . If that is the case, why not define the model that default_assignee is just user. Afterall, only the dropdown (in /app/views/_projects/_form.rhtml) loads data from Members anyways.
Thank you and kind regards
Updated by Douglas Campos over 15 years ago
Hi Adam!
Thanks for looking at this! As I've told, this is a WIP fork...
Anyways, your suggestion rocks! I will implement it ASAP. Now I'm digging the insides of redmine, there's always room for improvement in my code!
Again, thank you for taking the time to review this.
Updated by Douglas Campos about 15 years ago
I've almost finished it (more tests maybe?)
Can someone review it again? (http://github.com/qmx/redmine/tree/ticket-482)
Thanks
Updated by Eric Davis about 15 years ago
- Status changed from New to 7
- Assignee set to Eric Davis
Thanks, I'll do a quick review of the patch.
Updated by Adam Piotr Żochowski about 15 years ago
I am running this on my Redmine without problems.
With patch #3461 I now have a setup that I enjoy.
Anyone can create Issue
Issue is auto routed (based on category / default assigned to)
That person either approves the issue (and re-routes to developer), or rejects it
Eric, is there anything I can help with to have this included into official Redmine. I can provide you with udiff for 0.8.4.
Kind regards
Updated by Gregor Bader about 15 years ago
Eric Davis wrote:
Thanks, I'll do a quick review of the patch.
+1
Would like to see this in main branch. Another option would be to set the "Assigned to" field mandatory.
Updated by Alex G. about 15 years ago
Eric Davis wrote:
Thanks, I'll do a quick review of the patch.
+1.
Maybe it makes sense to have a global setting per project with an ability to overwrite it by the tracker setting (like of defaulted assignment on the tracker level is not set then we user project defaulted assignment)?
Reason is that there could be different departments (support groups) by tracker type - like 1st line support, technical support, R&D...
Updated by Robert Chady about 15 years ago
I have a strong dislike for patches in an actively developed application. For this reason, I took a stab at converting this patch to a plugin. It will require an update anytime views/projects/_form.rhtml changes due to it overriding the core one.
I've requested a new hook (#3735) to be added to get around this.
The plugin was written against the latest trunk version and is at git://github.com/rchady/redmine_default_assign.git. Comments are welcome.
Updated by Karlis Vitols over 14 years ago
We would be very greatful, if you could provide feedback, if this feature is to be resolved in nearest 2-3 months?
Updated by Anton Statutov over 14 years ago
The Plugin doesn't work with the latest Redmine version. I'm still searching the solution. Anybody have one?
Updated by Paul Dann about 14 years ago
Anton Statutov wrote:
The Plugin doesn't work with the latest Redmine version. I'm still searching the solution. Anybody have one?
The plugin works OK for me. Did you run the database migration that is required by the plugin? (rake db:migrate_plugins)
Updated by Raffaello Pelagalli about 14 years ago
- File default_assignee.patch default_assignee.patch added
Didn't saw this issue before making the patch :)
Here is a patch for this
Updated by Oli Kessler almost 14 years ago
Raffaello Pelagalli wrote:
Didn't saw this issue before making the patch :)
Here is a patch for this
The patch works fine for 1.0.2.stable, thank you.
The I18N is missing, though - we had to add translations in the file "config/locales/en.yml" (and other locales):
field_default_assignee : Default Assignee
Updated by Oli Kessler almost 14 years ago
The project jumpbox seems to be affected by this patch - it will just show the projects, this user is assigned to as the default assignee instead of all the projects.
This is due to the line has_many :projects, :foreign_key => 'default_assignee_id', :dependent => :nullify
in the user model. Is this behaviour intentional or just a side effect?
Updated by Frank Harper over 13 years ago
Oli Kessler wrote:
The project jumpbox seems to be affected by this patch - it will just show the projects, this user is assigned to as the default assignee instead of all the projects.
Oli, I just installed the plugin (not the patch) and haven't noticed any problems yet. By project jumpbox do you mean http://hostname/redmine/projects? This is where a user lands after clicking on "Projects" in the header.
Updated by James Robertson over 13 years ago
- Status changed from 7 to Resolved
- % Done changed from 0 to 100
This was implemented in the core product some time ago.
"Default assignee" drop-down list of "Information" tab of "Settings" tab for a Project
Updated by Etienne Massip over 13 years ago
- Status changed from Resolved to New
- % Done changed from 100 to 0
I think it's a plugin, I don't have such setting.
Updated by Cornell Wright about 13 years ago
+1
This is really a necessary feature. For us, issues tend to get lost sometimes until someone goes back and assigns issues without an assignee.
Etienne Massip wrote:
I think it's a plugin, I don't have such setting.
Does anyone know what plugin this is? This would solve my problem. I can't seem to find it in the plugins directory.
Updated by Paul Dann about 13 years ago
You might be after this: https://github.com/rchady/redmine_default_assign
Updated by Dave Lowndes almost 13 years ago
The plugin doesn't work for me either. It shows up, gives me a setting for the project but the setting's not saved and I still don't get a defaulty ehn creating a new issue. Would be nice for core please!
+1
Updated by Paul Dann almost 13 years ago
You could try using my fork on Github (https://github.com/giddie/redmine_default_assign). Rchady seems to not be maintaining his repository any more, and it's broken with the latest Redmines.
Updated by Radek Antoniuk over 12 years ago
Guys, I know that you have little development time but...
Please at least set sensible "expected" version or dates ... or merge... or do anything. For now there are already 3+ tickets for this that had been assigned, re-assigned, dis-assigned and so on...
Updated by Stéphane Thomas over 12 years ago
+1
Could this be be released in trunk?
Updated by Chris Roemmich about 12 years ago
I've updated the plugin Paul posted for Redmine 2.x.
https://github.com/croemmich/redmine_default_assign
Updated by Andreas M almost 12 years ago
Chris Roemmich wrote:
I've updated the plugin Paul posted for Redmine 2.x.
https://github.com/croemmich/redmine_default_assign
Thank you very much for this update. It works really great and should be included in redmine directly, or at least in the plugin list, as the original version works only for redmine <1.4
Updated by Sylvain Langlade almost 12 years ago
I wanted to post this on the project's github page, but miserably failed to do so. here is a small contribution to this plugin : a french translation. Just add a config/locales/fr.yml file in the projet with the following content :
# French strings go here for Rails i18n fr: field_default_assignee: "Assignement par defaut" default_assign_text_settings: "Options" default_assign_settings_help: "Assignement par defaut pour les nouveaux projets" label_user: "Utilisateur"
And thanks for this great plugin. It really should be included in redmine directly !
Updated by Paul Dann almost 12 years ago
Thanks Sylvain; I've added it to my repo: https://github.com/giddie/redmine_default_assign. I've also pulled in Andreas's changes.
Updated by Dipan Mehta over 11 years ago
+1. I do use the default assign plugin, but wont it be a great utility in Redmine core?
Updated by Anthony Lara about 11 years ago
Can we use this plugin if we installed Redmine with the package Bitnami?
Updated by Anthony Lara about 11 years ago
I've installed the plugin, bit when i want to click on "configure" (in page Plugin), i Have got the 404 error, why?
Updated by Paul Dann about 11 years ago
Thanks for reporting the problem. FYI, this page is for the Redmine feature request. For future bugs in the plugin, please create an issue here: https://github.com/giddie/redmine_default_assign/issues
I can see the same problem, and I'll fix it soon.
Updated by Toshi MARUYAMA about 11 years ago
- Related to Feature #13789: default assignment added
Updated by Gurvan Le Dromaguet about 11 years ago
+1 per project auto assignment is a must have for me
Updated by Miodrag Milic almost 11 years ago
+1
The default person should be placed for each Tracker.
Updated by Vitaliy S over 10 years ago
+1
there must be either auto assignment to person or group (by round robin rule, one from the group should be assigned)
No progress within 6 years, impressive.
Updated by Viktor Berke over 10 years ago
+1
Seriously, how more trivial could it be to add an option to make << me >> the default assignee?
Updated by Fred B almost 10 years ago
Any developpement? Well it's been 6 years! ;)
Updated by sch uess over 9 years ago
+1
A per-project "default assignee" setting (not a must, though)
Updated by J Bolt about 9 years ago
Is it possible to have this update to a selected pool of assignee's when the status changes say from "In Progress" to "Resolved" so that it will automatically show up for testing and closure (original assignee doesn't have to choose who gets it next... requiring them to actually think... ;-) ). I seen this featured asked for before but haven't seen it implemented well and having a single plugin to do both auto assignment on creation and resolving would be ++.
Updated by Wim DePreter about 9 years ago
J Bolt wrote:
Is it possible to have this update to a selected pool of assignee's when the status changes say from "In Progress" to "Resolved" so that it will automatically show up for testing and closure (original assignee doesn't have to choose who gets it next... requiring them to actually think... ;-) ). I seen this featured asked for before but haven't seen it implemented well and having a single plugin to do both auto assignment on creation and resolving would be ++.
Your request seems like feature #3517 (not implemented yet).
There is someone in this issue who refers to plugin http://www.redmine.org/plugins/redmine_luxury_buttons (not free)
Updated by Toshi MARUYAMA about 9 years ago
- Related to Feature #3517: Assign an issue to person based on the issue status added
Updated by Emrah KAVUN over 8 years ago
Hi there,
I need this functionality. Shall I patch my Redmine 3.2 or is this integrated and I haven't seen it yet?
E
Updated by Paul Dann over 8 years ago
As far as I'm aware, your best bet is still to install the plugin at: https://github.com/giddie/redmine_default_assign
Updated by Felix Schäfer over 7 years ago
Please find attached a patch to add the functionality, including migrating settings from the http://www.redmine.org/plugins/redmine_default_assign Plugin if available.
Most things are comparable/copied from the default version mechanisms. The main difference is that there already are per-category default assignees. As per-category is more specific than per-project, category default assignee take precedence over per-project default assignee.
Updated by Jan from Planio www.plan.io over 7 years ago
- Target version set to Candidate for next minor release
- % Done changed from 0 to 90
This is something that has been requested by many users at Planio and it seems to be popular here on redmine.org as well. Let's include it in an upcoming release, maybe 3.4?
Updated by Go MAEDA over 7 years ago
Felix, thanks for sharing the patch.
I think it would be greater if there is a option "<<Current user>>" in the dropdown. It assigns new issues to the author of the issue. There are similar requests:
Updated by Felix Schäfer over 7 years ago
Go MAEDA wrote:
Felix, thanks for sharing the patch.
I think it would be greater if there is a option "<<Current user>>" in the dropdown. It assigns new issues to the author of the issue.
Thanks for the suggestion, this would be a nice addition.
I'm afraid this would bring some additional challenges too, as "<<Current user>>" would not handle the case were the author is anonymous (either because the project is open or because it was received by mail with the permissions override option). So if you add "<<Current user>>" as an option you would need to add a fallback default assigned to to make sure new issues created by anonymous will be assigned to someone too. I would prefer to handle this in a new issue to keep this patch small enough to be added quickly.
Updated by Go MAEDA over 7 years ago
- Target version changed from Candidate for next minor release to 3.4.0
Felix Schäfer wrote:
I'm afraid this would bring some additional challenges too, as "<<Current user>>" would not handle the case were the author is anonymous (either because the project is open or because it was received by mail with the permissions override option). So if you add "<<Current user>>" as an option you would need to add a fallback default assigned to to make sure new issues created by anonymous will be assigned to someone too. I would prefer to handle this in a new issue to keep this patch small enough to be added quickly.
Thanks for the detailed explanation. This patch looks good as the first step.
Many people have waited for this feature for years. Let's deliver this feature in Redmine 3.4.0.
Updated by Jean-Philippe Lang over 7 years ago
- Subject changed from default assignment setting to Default assignee on each project
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Resolution set to Fixed
Committed, thanks.
Updated by Go MAEDA about 7 years ago
- Related to Defect #26072: Set default assignee before validation added
Updated by Luis Blasco about 7 years ago
Hi,
I've updated two installations to the 3.4. version but I'm not able to find this new feature in the project settings. Where should I find it?
Thanks in advance.
Updated by Jean-Philippe Lang about 7 years ago
- File default_assignee.png default_assignee.png added
The default assignee wan be set from the first tab of project settings. The field shows up if you have assignable users on your project (eg. members with a role that is assignable).
This issue is closed, please open a new issue if it does not work as expected.
Updated by Luis Blasco about 7 years ago
Thanks for the explanation, Jean-Philippe. The issue was due to a plugin's conflict. Solved.
Updated by Go MAEDA almost 7 years ago
- Related to Feature #16351: Option to set default member for uncategorized issues added
Updated by Go MAEDA over 4 years ago
- Related to Defect #33113: Default version and assignee are not exposed via projects API added
Updated by Go MAEDA about 3 years ago
- Has duplicate Feature #13123: Assigned default user added
Updated by Go MAEDA over 1 year ago
- Has duplicate Feature #2558: Assign all new issues to myself added