Hi Mike: We always convert our issues to either tasks or projects. And we always add a task to a project. But we maintain a monthly "catch-all" project that we add the stand-alone tasks into. When we convert the issue and add the resultant task into the project, we specify start dates and duration in the task. If it extends beyond the end of the monthly catch-all complete dates, we move it into the next month's and so on. We also have a number of other catch-all projects, that are annual and which we use to contain various one-off tasks that pop up front time to time. For example, we will have various website maintenance work e.g FY18 Find a Specialist. Each time someone on that specialist team changes, we get the request, create a task and add it to that specific project. At any given time, we can easily view activity to date, costs etc. etc. Plus wth all of those type of projects we can see exactly what kind and amount of resources have been utilized. To us, having an issue floating around without being able to easily categorize it for analysis or searching can be more cumbersome than creating the task. Bill Gattinger ATB Financial Edmonton AB wgattinger@atb.com