When tracking bugs in websites, most of the time the brand and model of the device is not really important, so i don't see why it should be a mandatory field. Is there some reason why you can't report a bug without filling these fields?

It would be nice to create templates based on certain fields we would like to report for our bug per company. Have the ability to create our own type of drop down type of issue, and remove the step to reproduce and the description labeled as issue and expected results the responsive of the issue. Reproducibility to remove and severity not to appear at all. And to have the reporter to have the name and date and time.

Great product so far. Just starting to use it.
For the test plans view, it would be helpful to have a way to export the test plans as PDF and/or CSV files for sharing and tracking work

In the test plans page, I can see a name, the generated URL etc. I would really like to see the status of the test plan - has any of the testers started working? How much have they covered? when did they start? etc.

Hi,
I have an idea to better categorize tasks. Sub-projects and sub-tasks.

1) Sub-project should act like "folder" inside a Project, in order to group a series of tasks all related to a specific topic (for example, "checkout bugs" or "Performance issues", etc.)
2) Sub-tasks are similar but with a minor impact. It happens that a task (e.g. registration process) could be splitted in 2-3 other sub-tasks like "registration form", "privacy agreement", "set main preferences" (it's just a fake example) that sholud be related each other. We should have a link in Main one to each of his children, and maybe, "solving" all sub-tasks results in solving that the main one.

What do you thing about it?

I do not see what the role's differences are - without trying myself ...

The number of bugs and other stats under Project Stats, does not appear to get updated at the same time the Bug List is updated with the new bug. While this is a minor issue, it does put the Project Stats out of sync with the Bug List for a time until the page is refreshed (when Project Stats gets updated).

Sometime is useful to add HTML code in tickets or in comments. I tried but actually is not possible neither using BLOCKQUOTE or PRE html tags. Code will be always interpreted....

When we invite a new user or the user creates a new account, the confirmation email is not being received. The same happens to send a new bug to a developer or project manager.

Help us please, because this problem is harming the continuity of our work.