This will no longer be needed once the capability to have issues on the board is re-released. This can be closed.

I would like the ability to bulk convert issues to tasks and keep the original requestor. Use case (software development): after regression testing cycle, many issues are released into production. We move the open issues as tasks to the backlog but currently have to do them one by one. I would like ...

This is a large need for us. We have a couple of teams that would better lend to Kanban but are not able due to system limitations. To add here, we'd want the ability (not required) to set due dates on stories rather than having to do a sprint that dictates the dates. To be clear, some teams would s...

Agreed, you should be able to pick and choose within user templates and teams what statuses are available.

Yes! We especially need bullet lists!

I would like the capability to see how far down the backlog we could get based on an average team velocity (in points). For example, there could just be a line below showing where you could get to in each sprint. This would be very helpful to predict what stories can be in an upcoming release.

Yes! Agile should not be related to planned hours. I'd at least want the option to toggle this. This is a huge pain point for me every sprint and I have to put fake hours on my stories so that the points show up correctly. Otherwise the points get altered. On that note, points should never dynamical...