Redmine

This can be implemented pretty easily as it seems.

You have to edit

apps/models/issue.rb

  safe_attributes 'project_id',
    :if => lambda {|issue, user|
      if issue.new_record?
        issue.copy?
      elsif user.allowed_to?(:move_issues, issue.project)
        Issue.allowed_target_projects_on_move.count > 1
      end
    }

  safe_attributes 'project_id',
    :if => lambda {|issue, user|
      if issue.new_record?
        true
      elsif user.allowed_to?(:move_issues, issue.project)
        Issue.allowed_target_projects_on_move.count > 1
      end
    }

I am not sure if there are any side effects, so use this hint at your own risk :-)

Hi Bastian
The patch is working great. However, I hit another wall. I have project1 with only tracker1, and project2 with tracker2. Then from project1 I create a subtask in project2, I expect that the subtask will be tracker2 but it is not possible since the tracker list show only tracker1. Could you find the way for the tracker to be refreshed according to the selected project? Thank you very much
Quan

I too have tried this approach. It's definitely nice and would be the optimal way to go for those who organize everything with a boat-load of projects. I haven't noticed the issue that @Quan has mentioned. When the project is changed in the drop down, the javascript is executed and the correct form is loaded for that project–i.e. the correct fields and correct options.

However, my app has some plugins installed that have some fields on the issues form (particularly redmine_tags), and when the form is loaded for the new project, the plugin's field isn't correctly stylized (as a taggable select list). Essentially, the plugin's javascript is run when the page first loads, but when a new project is selected in the drop down, the plugin's javascript is not rerun as it should be. I haven't been able to track down where these hooks are made nor have I been able to add a js hack that could make the right calls. If this were to be fixed, this would be the way to go for me, but I can't have the tags field broken; it renders it useless and confusing.

+1
This is exactly what we need, it is huge effort to navigate between projects, especially when creating subtasks.

Sebastian Paluch wrote:

+1
This is exactly what we need, it is huge effort to navigate between projects, especially when creating subtasks.

That patch file not working on latest version of redmine.

Bastian B. wrote:

Patch that enables to configure the behavior (to select the project) via the settings.

Do u have the updated patch file ?

The patch does not work due to a change done in r13999. The r13999 has actually implemented necessary change from the patch making project_id safe for new form but at the same time it has restricted project drop down for new issues by !@issue.new_record? in views\issues\_form.html.erb:

<% if @issue.safe_attribute?('project_id') && (!@issue.new_record? || @project.nil? || @issue.copy?) %>

<% if @issue.safe_attribute?('project_id') && (@issue.new_record? || @project.nil? || @issue.copy?) %>

Does anyone see something that could prevent from applying this?

...and related to #1003.

Just wanted to check if above is Ok i.e. removing !@issue.new_record from the form. Should I do this in my install?

Could you provide a plugin for this or integrate it into the core, please?

That patch file not working on latest version of redmine. Do you have the updated patch file ?

Manuel Morales wrote:

Do you have the updated patch file ?

Do you mean this? (It works with redmine-3.3.1.)

diff -up redmine-3.2.1/app/views/issues/_form.html.erb.orig redmine-3.2.1/app/views/issues/_form.html.erb
--- redmine-3.2.1/app/views/issues/_form.html.erb.orig  2016-03-13 18:18:44.000000000 +0100
+++ redmine-3.2.1/app/views/issues/_form.html.erb       2016-06-08 16:36:32.921088980 +0200
@@ -8,7 +8,8 @@
 </p>
 <% end %>

-<% if @issue.safe_attribute?('project_id') && (!@issue.new_record? || @project.nil? || @issue.copy?) %>
+<% if @issue.safe_attribute?('project_id') #&& (!@issue.new_record? || @project.nil? || @issue.copy?)
+%>
 <p><%= f.select :project_id, project_tree_options_for_select(@issue.allowed_target_projects, :selected => @issue.project), {:required => true},
                 :onchange => "updateIssueFrom('#{escape_javascript update_issue_form_path(@project, @issue)}', this)" %></p>
 <% end %>

Thank you Gret T,

But I made the change, and even is not working.

Could you send me, your apps/models/issue.rb changes? My version is Redmine 3.2.3.stable

I appreciate your help.

Greg T wrote:

Manuel Morales wrote:

Do you have the updated patch file ?

Do you mean this? (It works with redmine-3.3.1.)

[...]

Thank you Gret T,

But I made the change, and even is not working.

Could you send me, your apps/models/issue.rb changes? My version is Redmine 3.2.3.stable

I appreciate your help.

Greg T wrote:

Manuel Morales wrote:

Could you send me, your apps/models/issue.rb changes?

I didn't change that. I attach project-select.patch modifying issues_controller.rb.

Thank Greg T for you answer,

I change the file and restart the Apache service, but when new issue are created, it don't show selection field for projects only when copying or edit issues.

Do you have any idea or suggestions?

Manuel Morales wrote:

Do you have any idea or suggestions?

I'm afraid I don't. It works for me.

+1

Hi, Marius. Your patch is exactly what I am looking for. Which Redmine Version do you use. I am using 3.2.1.stable. By using your patch I've got 2 FAILS:

patching file app/models/issue.rb
Hunk #1 succeeded at 1397 (offset -108 lines).
Hunk #2 succeeded at 1413 (offset -108 lines).
patching file app/models/project.rb
patching file app/views/issues/_form.html.erb
Hunk #1 FAILED at 9.
1 out of 1 hunk FAILED -- saving rejects to file app/views/issues/_form.html.erb.rej
patching file test/functional/issues_controller_test.rb
Hunk #1 succeeded at 1604 (offset -208 lines).
Hunk #2 succeeded at 1628 with fuzz 1 (offset -208 lines).
Hunk #3 succeeded at 1663 (offset -207 lines).
patching file test/unit/issue_test.rb
Hunk #1 FAILED at 354.
1 out of 1 hunk FAILED -- saving rejects to file test/unit/issue_test.rb.rej

+1

Michael Weiss wrote:

Hi, Marius. Your patch is exactly what I am looking for. Which Redmine Version do you use. I am using 3.2.1.stable. By using your patch I've got 2 FAILS:

Hi Michael,

The patch was made against current Redmine trunk and it wasn't tested on 3.2.1 or latest 3.3.3. Hopefully, the patch will be taken into consideration for a future Redmine version.

Mischa The Evil wrote:

I like the change proposed by Marius BALTEANU in note-23. Setting target version to 'Unplanned'.

Thanks for the feedback, Mischa. Looking forward to see this proposed for a future version.

Is there any chance of this making it into the main? With microservices and multiple interacting systems it is only natural that one parent task is going to require changes in multiple other projects.

It is a clunky process to create the issue and then edit to change project each time as notifications are triggered etc...

I have tried out the patch and think there isn't any problem to include this feature in the upcoming release. Users will be able to create a subproject's issue when they see the parent project's issues list. I can easily imagine the use case and usefulness of the feature.

The only thing I was worried is that adding a new UI element, the "Project" drop-down, increases the complexity of the new issue form. But I found that it was needless anxiety because the drop-down is displayed only when the project has one or more subprojects.

This is long waited feature, thanks for implementing it.

The only issue it seems to have is that the select list will not preserve project hierarchy by not showing intermittent projects that do not have trackers enabled (or user has no access to). As a result we get flattered list of projects. This is an issue when we have deep hierarchy with "container" projects in between and sub-project names are not unique, on its own not allowing to clearly identify the project.

It would be good if all projects are shown but select items for those where issue cannot be added are disabled and grayed out.

Similar issue exists in project jump box (#8904).

what i have to change to get the project dropdown for any project (including projects without subprojects)? u should be able to choose every project, not only subprojects. is this possible?

Environment:
Redmine version 3.4.5.stable
Ruby version 2.3.1-p112 (2016-04-26) [x86_64-linux-gnu]
Rails version 4.2.8
Environment production
Database adapter Mysql2
SCM:
Git 2.7.4
Filesystem

thank u very much for ur help