ENHANCEMENT Ticket (closed)

Difference between 'tasks' and 'tickets' regarding 'solutions'

The 'tasks' and 'task lists' approach in ProjectPier is literally a 1 line sentence or maybe a paragraph. Simplying viewing a task list and clicking 'add task' would stretch down to display a box where you type the new item with the 1 _option_ to assign it, emphasis on this being only an option. Although there is definately something to be said about having a very error/solution approach certain aspects of general business project management SHOULD be a matter of jotting down a note. Perhaps the choice of what options are available to this task list? So I create a 'Bugs' task list with the option to input resolution, version, urgency or attach whatever. But honestly sometimes adding a task should be quick, painless easy and the fastest thing you could possibly do. It's a matter of jotting down a note and can sometimes be a matter of checked and unchecked. Giving the option of how much is thrown in front of them I think is nicer although may be complex, but I know I don't want to see 20 forms/inputs whenever I add a task each time especially when I'm used to the simple viewing of a task list and the "quick add" link letting me fill in 1 textarea and an ajax update. The whole thing doesn't need to be reproduced I just want to emphasize the option of ease and simplicity. #### Edit I'm wondering... perhaps it should be considered to make tickets (like trac) for software development a plugin/module/optional component. Although this is nice it is for software development mostly it is thought of as a side feature of business project management. Having a trac-like approach isn't bad but I also want simplicity too so maybe this should be pondered.
on 03.22.09 reported by: ProLoser
on 03.22.09 by ProLoser
- **description** was changed
on 04.15.09 by Theaxiom
- **status** was changed to _fixed_ this feature is being revised in 0.5