Hello. I'm trying to make requests to the API. Access Token was successful, however, resorting to other methods get a server 500 error on your part . What could be the problem? Sorry for my English. Thank you

Hi

Firstly thanks for all the changes you have made.

Is it possible that when you select Report Bug during the test run, the steps you created during test case set up can pull through to the bug report. The user should still be able to edit the steps at this point. This change will increase tester productivity as they do not need to retype the steps already set up in detail.

Regards

Clarise

Hi,

I was using tool and it is great. But how to remove component from my test plan? For example, now I have 3 or 4 component that I don't need in my test plan, but I don't know how to remove them.

Currently user has to "Add another case" then drag the new row all the way up.

It would be nice to be able to create a new version when reporting a bug. I always forget that I haven't added the new version to LT until I've already filled out several fields on a bug and then have to cancel to add the new version to the project.

Thanks!

I have an ios application which does not compile while using the lib.

Does someone know something about it?

Any chance you will add web hooks where I can specify my own url? Like the Slack integration, but I want to post to my own legacy system.

Best regards // Matt

For each web testing project we have a standard set of test cases. I need to run these tests on each project, currently I have to copy and paste all individual test cases into a test plan for each project, which is ridiculous.

Is there not a way to copy test plans between projects, or even duplicate a project???

I love LeanTesting, but the dashboard is so oldschool.

What I propose is to add a new view, to permit to developers to only see tickets where he need to answer or work.

Developers should have theses columns:

- Waiting customer ( tickets where we waiting a feedback from the customer )

- Answer required ( new ticket or new question / comments from the customer )

- Working tickets ( In progress & confirmed ticket )

So, the developer only focus on the "answer required" column, where he could easily answer, then the ticket go back to "waiting customer" column.

The "Answer required" column should always be empty, if not, it's a priority, to improve the workflow process.

When a ticket is solved, it's moved in the "waiting customer" column.

Customers should have theses columsn:

- Waiting developer ( tickets not yet readed/answered by developer )

- Answer required ( question/comments where the developer waiting a feedback )

- Working tickets ( In progress & confirmed ticket )

IMHO, this way seems to be more useful for developers & customers.

Regards,