Let change status be a visible dropdown. Right now it looks like simple text.
Let change status be a visible dropdown else we are being made to do two clicks as compared to one in the previous version. One click to highlight or show the dropdown and the second to select. The title above which indicates that this text is "actually" a drop down can be easily ignored by the eye while working quickly. If one has to look at text to just figure out if a drop down is a drop down this is NOT COOL. This impedes UX a bit while working on a lot of bugs. Please consider fixing this. thanks
Fixed in version
Hi,
I am not able to understand with which logic the "fixed in version" dropdown appears.
I'd like to set it in one of the statuses I defined.
Thank you.
Copy Paste Sceen Shots
Can you provide the ability to copy paste screen shots directly onto the bug instead of attaching a file? Attaching a file involves saving it and them attaching it either by file selection or drag and drop which is quite simple........However some of our staff tend to copy paste the screen shot into a separate email outside of LT and send it to the concerned party, which defeats the purpose of using the tool.
Error type problem When upload selenium IDE
For fail upload testcase via selenium ide it should be display error type with description..
[ADD BUG] change order or componets & status
While you do not have the ability to sort the components or status, at least make them alphabetical by default. Then we can rename them to change the order
option to reopen a bug
An option to reopen an already existing bug would ease out the process of reporting the bug again
Bitbucket include the link of commit.
Thanks for Bitbucket integration,
I would like if you could add the link of the commit as post inside the the bug, with full comment of the commit.
Custom fields
I'm working for an elearning company. The bug tracker we are currently working with allow us to create different custom field (String, list, checkbox, numeric, drop-down menu).
For exemple, we have a ''Departement ID'' that allow us to select from a drop down menu the departement that are responsible of the issue. (Production, programmation, Pedagogy...)
We also have a string custom field that allow us to write the screen number where the issue was found. We often have 100 screens projects, so it would be hard to put them into the 'tags' section. We also need to see the screen number (and some of our other custom field content) in the bug list table.
Allow a user to terminate a test if a step is blocking
If there is a status of could not test (or preferably "blocking") then a test can be terminated without needing to perform the rest of the steps (while still recording the previous test). When this occurs the test is reset to "start" rather than resume.
Служба підтримки клієнтів працює на UserEcho