...

Well, the way you organize your tests may be achived in several ways. Your organization should start by classifying your tests individually so you can easily find and filter them out.

At Test level

Classify your Tests

• use use labels to  to tag your Tests (or your Test Sets); if you start having many testers and your project grows, having a well defined list of labels may help
• use the the priority field field, so you can distinguish between tests
• assign the Test to the proper component

Using Test Sets

Organize Tests in Test Sets

• group tests in as many Test Sets as make sense to you, either because they're testing the some feature, or the same UI component, or if they exercise the most critical use cases
• classify your Test Sets, similarly to what you did for Tests

Organizing Tests for regression testing

• you can create a Test Set for this purpose and add a specific label (e.g. "regression") to it, and then you tests for requirements of previous versions
• you can create a "regression test setTest Set", for each version, by cloning the previous version regression test set and add more tests

...

Example: you're working on product v3.0 and want to do regression testing to make sure you have not broken anything. If the previous version, v2.0, had already some regression tests in a specific test set, then you can clone it and add some more tests for validating v2.0. 

Using the Test Repository