Redmine

Thomas Lecavelier wrote:

The target version field has to be set when it will actually part of the target release.

I can relate this solution/workaround that works, but it is for the whole instance, not by proyects.

http://www.redmine.org/boards/2/topics/18781?r=36152

Regards.
Nestor

+1

It would be great if this patch can make it in 3.4 release! Now that we have the option to specify a "default version" for new tickets (since 3.2) it makes sense to also add a project setting to chose the default tracker for a new ticket in this project.

Now that we can restrict on which trackers the different roles can create issues, wouldn't it make more sense to set the default tracker on each project member? And maybe add an optional default tracker on each role so that members can automatically inherit this default tracker, but still overridable.

Jean-Philippe Lang wrote:

[…] wouldn't it make more sense to set the default tracker on each project member?

What would be the use case for default tracker per project member? I don't see such a business case.
If I remember it correctly, there's not a single project setting which can be set per project member – everything is based on the project members role.

And maybe add an optional default tracker on each role so that members can automatically inherit this default tracker, but still overridable.

This makes more sense to me than per project member. Also when taking into account your first statement:

Now that we can restrict on which trackers the different roles can create issues […]

Despite everything, my personal oppinion is that a default tracker per project is enough, because I think the workflow/settings/roles&rights configuration process shouldn't get overconfigured any further.

When talking about default tracker per project member, you could also think about default versions per project member… No… this is just too much…

This would definitely be quite handy here.

I constantly have users -- heck, even myself occasionally, set the tracker wrong on bug creation.

I'd say that on a given day, out of 100 bugs -- 20 extra emails go out for a tracker change. That's unneeded distraction, so... I throw my vote towards this. If there is a vote.

Just to clarify, it's the 'default of nothing' that is very needed here. To FORCE a user to set something...

+1 for "default to nothing, force user to select something".
Would be very useful to prevent creating tickets with wrong tracker.

+1 for "default. If nothing, force user to select one. NOT select the first element with NO real criteria".

Better: set available trackers for project and Rol (with defaults).

+1

Set a default tracker in each project.
A default tracker can be nil.
If a default tracker is nil, the user MUST select one tracker.

I would prefer a default tracker per project (and maybe per role, as in #11652) – any chance to get this into Redmine 4.0, either as patch, or as plugin? This would be highly appreciated; I guess it's not possible any more to apply the diff from #1365…

Since there is a patch available now, please schedule it for one of the next releases.

Mathias Walter wrote in #note-15:

Since there is a patch available now, please schedule it for one of the next releases.

Redmine 5.1.1, patching return error:

root@redmine5:/opt/redmine# patch -p0 < 1667-20231031.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/app/helpers/projects_helper.rb b/app/helpers/projects_helper.rb
|index d4f7339a0..b9867fa3d 100644
|--- a/app/helpers/projects_helper.rb
|+++ b/app/helpers/projects_helper.rb
--------------------------
File to patch:

If i force the path to the file, the following error occurs:

File to patch: /opt/redmine/app/helpers/projects_helper.rb
patching file /opt/redmine/app/helpers/projects_helper.rb
Hunk #1 FAILED at 123 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file /opt/redmine/app/helpers/projects_helper.rb.rej
can't find file to patch at input line 24
Perhaps you used the wrong -p or --strip option?

Dmitry Nekrasov wrote in #note-16:

Hunk #1 FAILED at 123 (different line endings).

This looks like you've downloaded the patch or checked out the repository with different line endings (LF vs CRLF).
Also, the file is indeed there app/helpers/projects_helper.rb.