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.

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

I would like to see this feature in redmine.

I'm looking at this now....patch is comming soon

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.

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

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: ran
alter table projects add default_assignee_id int;

/app/models/project.rb: added line
has_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

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.

I've almost finished it (more tests maybe?)

Can someone review it again? (http://github.com/qmx/redmine/tree/ticket-482)

Thanks

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

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.

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...

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.

We would be very greatful, if you could provide feedback, if this feature is to be resolved in nearest 2-3 months?

The Plugin doesn't work with the latest Redmine version. I'm still searching the solution. Anybody have one?

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)

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

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?

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.

+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.

You might be after this: https://github.com/rchady/redmine_default_assign

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

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.

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...

+1

Could this be be released in trunk?

+1 This would be really neat.

I've updated the plugin Paul posted for Redmine 2.x.
https://github.com/croemmich/redmine_default_assign

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

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 !

Thanks Sylvain; I've added it to my repo: https://github.com/giddie/redmine_default_assign. I've also pulled in Andreas's changes.

+1. I do use the default assign plugin, but wont it be a great utility in Redmine core?

Can we use this plugin if we installed Redmine with the package Bitnami?

I've installed the plugin, bit when i want to click on "configure" (in page Plugin), i Have got the 404 error, why?

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.

+1 per project auto assignment is a must have for me

+1

The default person should be placed for each Tracker.

+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.

+1

Seriously, how more trivial could it be to add an option to make << me >> the default assignee?

+1

Any developpement? Well it's been 6 years! ;)

+1
A per-project "default assignee" setting (not a must, though)

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 ++.

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)

+100!

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

As far as I'm aware, your best bet is still to install the plugin at: https://github.com/giddie/redmine_default_assign

+1

+1

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:

• #482#note-45
• default 'Assigned to:' without categories

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.

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.

Thanks for the explanation, Jean-Philippe. The issue was due to a plugin's conflict. Solved.