Default tracker setting in each project
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.
#2 Updated by Nestor Lobo over 9 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.
#5 Updated by Tobias Fischer almost 6 years ago
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.
#6 Updated by Jean-Philippe Lang almost 6 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.
#7 Updated by Tobias Fischer almost 6 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…
#8 Updated by Brad Barnett about 5 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...