Currently, it looks like various platform details on the bug-tracker form are out-of-date.

For example, the highest iPhone model is 7 when it should be 8 or X, the highest iOS is only 10.2, the highest Android version is 7.1 which should be 8.1 etc.

It would help our bug reports to be more accurate if we could enter the correct details for newer phones.

Thanks.

Some external testers have corporate internet policies that are blocking lean testing invitations. Would like ability to create and copy a invitation link, so I can paste it and email it from my email system.

It would be beneficial to be able to have an "Expected Result" and "Actual Result" against a test step and not just the whole test case. I'd like to be able to fail on a step rather than the whole test. 

Would improve the usability significantly if the designated administrator could configure which bug fields were mandatory for a project. For example, the make and model of PC is rarely of interest and we only seldom want to add an attachment. Currently have to fill the mandatory fields sometimes with dummy data.

I'm loving the system.
Soon I will make an acquisition of some paid resource as an incentive
Congratulations!

It would be nice to be able to group test plans into finer categories than components.  For example, I have each page of my manually-coded web site set up as a component.  I'd like to be able to group the test plans within the component, so that I can have sub-components like: menu system, header, footer, etc.  This would make it easier for me to track which parts of a web site are giving me problems.

The account manager started and saved a test run. But it seems that this role cannot delete test results, not edit test results.

I've turned off "Strict Test Runs" to allow other users to edit test results by others, but they cannot delete those test results non run/created by them.

So, how can I remove the test result accidentally created/saved by the Account Manager?

After submitting a bug I first need to save the whole testcase en press 'edit' again to log a second bug because if I try to log more than 1 bugs in once the dropdown list of the field 'device' is empty, so I can't submit. Our whole testing team is encoutering this problem. 

Besides this, the attachement field stays mandatory although we switched it off. We can;t submit a bug without adding an attachement. 

- We've got a bug when logging a bug the drop down lists in the fields 'device', 'model', 'device type', 'OS' are empty, we can't submit the bug. We need to log in and log out again and sometimes we're able to submit. 

If you select a device at the top of the test run to be the default device for all reported bug, the device selector in the bug reporting page will break after reporting 1 bug. It seems the only way to fix it is to save the current test run and then click "edit run" again.