Or, assign to front-end group and whichever developer is free next grabs that bug.

I just noticed that you can add a new version when specifying the "Fixed In" version, when completing a bug. That's pretty sweet!

For my own reference, the link is now https://leantesting.userecho.com/topic/473219-formatting-of-text-in-bugs-detail/ :D

Woohoo!

Isn't that up to us to decide about our own projects?

Also, what about feature requests? They don't necessarily have a version dependency.

The ability to create lists would also be very useful.

You can use the "Type" field for this purpose.

Woohoo!

Bug statuses can now be customized. I created several "Closed" statuses like "Not A Bug", "Won't Fix", etc.

Yes please! I'm sure this isn't a common use case, but it's a huge pain when it becomes necessary.

For instance, I have been collecting all manner of bug reports to one project, covering the entire application. Now, management would like to tackle all of the UI changes all together. So, I figured it'd be easiest to just move those particular bug/feature reports to a new "UI Redesign" project.

I suppose I could use sections for this purpose, but I'm currently using sections for, well, different sections with the application. For instance, "Calls", "Requests", "Admin" -- different areas of the program. This would get messy if I was also using it to organize different kinds of issues.

In this particular case I suppose I can change the "Type" to "Visual", but that again clashes with the use of that field for, e.g., UI bugs. And this is just an example. All uses won't have that workaround available.