What's the best way to handle multiple to-do lists

[Jacob Peebles]

We currently use basecamp for to-do lists and basic task management. In basecamp we can create a new list, populate, finish it, and then kill the list off. Basically many of the lists are one time, short lived tasks.

How is that best handled in JIRA core? Would it get messy to have to create a new to-do project each time you want a new list, and then finish it off in a matter of days? Is there a way to archive out these old projects so you can keep things orderly?

Basically, the question is if you have many small lists that are really short lived tasks list (not ongoing) what's the best way to handle that in JIRA.

Thanks,

Jake

[Steven F Behnke]

If you remove browse permissions for a project, users cannot seem them any more. Thus archiving these projects is as simple as adding an "archived" permission scheme. Admins can always re-use the previous scheme to bring the project back course.

If you find yourself needing a work area instead of a simple-task list, you can easily re-use a project as such. You can use Components, Versions, or a custom-field to delineate different objectives that these tasks are focused towards.

If you find your tasks are becoming more concrete business rules, you can define custom issue types that follow different flow steps, use different fields, etc. You can then use these types in addition or instead of Task.