Feature #4845
closed
Added by Kornelius Kalnbach about 14 years ago.
Updated about 11 years ago.
Description
When we managed a non-conding project using Redmine (organization of a conference), we added a "Task" tracker (and disabled the other ones). Later, I found the new tracker useful for my coding projects as well.
For example there are 3 tasks for an upcoming release (repository maintainance, improving documentation, and a design update for the website) which are neither a "Feature" nor a "Bug".
So, I propose that a new built-in tracker named "Task" is added to Redmine. The German translation would be "Aufgabe".
That's already implemented on Redmine.... even more ! You can create as much 'Trackers' as desired, and name them as needed. Of course, you can rename existing ones (changing their concept if you wish). All of this should be done by admins.
Antonio, he was referring to the 3 default trackers and proposes to add this one to those 3 default trackers.
- Assignee set to Eric Davis
- Assignee deleted (
Eric Davis)
I don't see a point in adding another default tracker. Which trackers one wants is highly subjective and project specific. There are many sensible setups, but Redmine can only provide one default setup, by the very definition of "default". The current one is not perfect (and can't be perfect according to what I just said), but it works, and it is super easy to customize for a new project. Since projects have to customize settings in any case, I don't see why this long-standing and proven default should be changed now -- at least not as long as there are no strong arguments as to why the change should happen.
So, just close this.
- Due date set to 2013-04-03
- Status changed from New to Needs feedback
Please give feedback until 3rd April. Otherwise I will close this request.
But well, I think everyone is free to define it's own trackers. The user isn't forced to use the default data.
- Status changed from Needs feedback to Closed
- Resolution set to No feedback
Closing this as there is no feedback on this issue. We thing this is resolved in current releases.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by