Hi Earl,

Thank you for your comment. You are correct - the test plan component is much newer and there are tons of improvements that we can make.

That is our strategy. We launch products early, we see if users appreciate them, what ideas they have to improve them, and then we build on the foundation.

The bug tracker was very basic in its beginning and has blossomed nicely over time. The same will happen for the test case management tool. We have tons of ideas to improve it, users have already made many great suggestions, all we need is a bit of time to make it happen :-)

And yes, import/export is high on the list.

Best,

Simon

Hi Matt,

I apologize for this inconvenience. Definitely your test plans are in your account somewhere - maybe under a new project, maybe under an existing project, but somewhere.

There were a few issues with the merge that arose but they have been fixed and everyone who was in a situation similar to yours eventually said: "found them!"

If you email me your organization name and username I can dig in a little more for you. Email us at: support@leantesting.com

Thanks,

Simon

Yep, we've thought about this.

While not as detailed as your suggestion, please vote for this suggestion here:
https://leantesting.userecho.com/topic/449183-add-ability-to-create-your-own-company-specific-statusses/

so that we can have only 1 entry to track.

Thanks,

Simon

can you be more specific about the context in which you'd like to do this? Give us an example situation. Thanks.

Hey Marcus,

We are video games guys as well :-)

We definitely have seen the types of projects where the bug bases are a huge mix of bugs related to different platforms - but that's not to say that we would recommend it as good practice.

In specific cases, yes, I understand where you are coming from and 1 project for all makes sense.

But I think that our role as makers of this software is also to push for best practices. It's not always accepted and we've had to make a lot of changes over time to give users more flexibility (in the first version, all fields in a bug report were mandatory, with no possibility to modify that) - but I still care deeply about at least leaning towards good practices.

I really think that the best way to organize your testing efforts is 1 project = 1 platform.

But I have been wrong in the past, so I'm leaving the door open :-)

Simon