Project

General

Profile

Actions

Patch #1667

open

Default tracker setting in each project

Added by Hiroyuki Yoshioka over 15 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2008-07-21
Due date:
% Done:

0%

Estimated time:

Description

Hi,

I made a patch which allow administrator to 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.

This patch solves #1365.


Files

default_tracker.patch (3.79 KB) default_tracker.patch Hiroyuki Yoshioka, 2008-07-21 07:04
test_default_tracker.patch (1.64 KB) test_default_tracker.patch Hiroyuki Yoshioka, 2008-07-21 07:04
1667-20231031.patch (12.3 KB) 1667-20231031.patch Minoru Maeda, 2023-10-31 03:54

Related issues

Related to Redmine - Feature #1365: Allow Project by Project setting of a 'Default' Tracker value including nilNew2008-06-03

Actions
Related to Redmine - Feature #11652: configurable issue tracker defaultNew

Actions
Has duplicate Redmine - Feature #19223: Add option to set default tracker for project on new issueClosed

Actions
Actions #1

Updated by Thomas Lecavelier over 15 years ago

  • Target version deleted (0.8)

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

Actions #2

Updated by Nestor Lobo about 11 years ago

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

Actions #3

Updated by Go MAEDA about 9 years ago

  • Has duplicate Feature #19223: Add option to set default tracker for project on new issue added
Actions #4

Updated by Go MAEDA about 9 years ago

Actions #5

Updated by Tobias Fischer over 7 years ago

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

Actions #6

Updated by Jean-Philippe Lang over 7 years ago

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.

Actions #7

Updated by Tobias Fischer over 7 years ago

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…

Actions #8

Updated by Brad Barnett almost 7 years ago

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

Actions #9

Updated by Toshi MARUYAMA almost 7 years ago

  • Subject changed from Default tracker setting to Default tracker setting in each project
Actions #10

Updated by Gregor Glashüttner almost 6 years ago

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

Actions #11

Updated by J. Pablo Zebraitis about 5 years ago

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

Actions #12

Updated by J. Pablo Zebraitis about 3 years ago

+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.
Actions #13

Updated by Albrecht Dreß almost 3 years ago

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

Actions #14

Updated by Minoru Maeda 5 months ago

I attached a patch with the following features:

  • Added a default tracker item in the project settings.
    • In the "Issue tracking" tab, you can set the default tracker "For all roles" or "By role".
  • When adding a new Issue, the default tracker is specified only once.
    • If the default tracker is not set or if 'Add issues' is changed to not allowed in the role, the tracker is specified as usual.

However, this patch does not implement the default tracker for the project's REST API .

Looking forward to your valuable feedback. Thanks in advance!

Actions #15

Updated by Mathias Walter 3 months ago

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

Actions

Also available in: Atom PDF