|
History
| Log In
|
|
|
|
We kind of do this at the moment, using the new Subtasks in JIRA
But we'd like to have a very lightweight version of them. The TODO items are just strings - no components, descriptions, assignees, etc... And the only status is Done/Not Done. Basically they are bullet point items that describe what needs to be implemented / tested / documented. A bit like the Tasks in outlook. We find that many time we want to add information regarding JIRA isssues like "do not forget to check that it works in X platform" or "the documentation has to be updated accordingly" - we can add them as comments or edit the issue description - but that is very easy to be missed by the developer. Adding a full-blown subtask involves too much overhead for such a simple thing. It's been two years since I logged this and every day I miss this feature. Hi,
I'm a developer in a company that uses JIRA for all our stuff. It would help me IMMENSELY if this little tidbit got added. Most of the tasks/bugs/etc. that I get have multiple steps to them. Many of them take days/weeks to finish, and most of the 'steps' do not qualify as individual/separate tasks, etc. In addition, while working on a particular task I often have to stop working at the end of the day, and come back to it in the morning. If there were a feature that allowed me to simply enter strings into a text box as 'todos', and later 'check' them off as I complete them I could note where I was when I stopped and easily come back to that spot in the morning. I could also add 'todos' as I work and discover milestones along the way to completing the task/bug, etc. Another reason to have this type of functionality is for tasks/bugs, etc. that end up requiring the assignee to do things not orignially thought of during task creation. A little 'todo' list just above the project description could ensure that anybody authorized to edit the issue could add 'todos' (and perhaps a small column to the right would record who added each 'todo'). This would ENSURE that these important things didn't get burried in a hail of other comments on the issue. Another way this would be helpful is in bug patching. I'm responsible for taking fixed files and updating the various RPMs they belong to. It's often quite difficult to parse through the comments of a task to find just what files were changed in the process of the fix. Something like a 'todo' list would allow the bug fixer (or myself once I've found them) to create a sub-task to the orignal problem, and add a 'todo' for each file. Although this type of thing could also easily be put in the description, or a comment for the task, a 'todo' list would very clearly seperate exactly what files need updating from all the other specifics of the sub-task. I'm sure there could be a dozen more uses for a feature like this. Any comments from Atlassian re. the possibility of this making it to a future version? If there still was a possibily of "sponsored development" I would definitely try to get sponsorship. And I really believe this very lighweight feature would be welcomed by everybody and make our lifes much easier. Paco,
This isn't in the next release (3.7) and that is really as far as we have scoped. The only alternative is to use sub-tasks at the moment. Cheers, Is there a forum for placing bounties on feature requests? If so, I'd certainly pitch in for this feature.
Our biggest knock against JIRA is that it's still not as agile or lightweight as Basecamp. While Basecamp is too lightweight for serious issue tracking, adding per-issue TODO check list capability fills in that gap. I hate that we have some developers that are still married to checklist oriented TODO list silos that remain disconnected from our JIRA installaion. This is rather a major issue that keeps our development team fragmented and less committed to using JIRA for future projects. Hi Jonathan,
The best place to put a bounty is to get one of the Atlassian partners to develop this for you as a plugin. There are Atlassian partners who specialise in extending JIRA. If you are interested please send an e-mail to: Cheers, Have you used the now famed Basecamp to-do list? (see http://www.basecamphq.com/demos/todos/
 for a demo) Of course we don't need anything near as fancy. But we do want something that is highly efficient and easy to use. This should essentially serve as extremely light-weight sub-tasks that might be weakly inspired by basecamp. Version 0.1 could be done w/o AJAX, but AJAX would be a soon-desired feature of the to-do list plug-in.
I look forward to your questions and help further refining the specs here. Screenshot taken from Basecamp's demo video:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Per issue TODO check list
This is not the same thing, and I'm sure you've thought of it... but here's what we do at work...
any thing that is 'too small to be an issue', or is strictly tied to one issue as a 'sub issue' of sorts, we would enter into jira as a "task". We really have no other use for this 'type', so we use it as our TODO type.
We've set up a link type called " Has TODO " and " is TODO of "
So when we create our 'issue' of type 'bug', 'enhancement' or 'new feature', we can then create 0...n issues of type 'Task' (TODO), and link them to the parent issue.
This does present a fairly nice 'list' of todo items in the links section of the issue. And you can see which ones are crossed off, as you complete them.
Of course, there's no workflow (I could close an issue that still has TODO tasks open).
But it "looks" about right.