We use TestFLO, which is a free Jira plugin. You can import/export CSVs, easy test duplication, assignment, etc, and you can tag requirements to the test cases and to send back to the devs. There are also a ton of charts that come with the free version, and an optional paid version with even more charts. We’ve been using it about 2 years for manual test management and it’s been really easy and useful.
@fioriniswann love to know more about the limitations that you found; just reach me (ask to talk to me) so I can see if I’m able helping you overcome those limitations somehow 
I am also still in a totally-non-automated testing situation and when I said, hey, I need somewhere to write tests so that we can record that we’ve executed them and keep them reusable, they said, well, what package have we already got that you could use?
So therefore they are in Jira. It’s not wonderful, but just the fact that I can easily link the tests I want to do to the scrum tasks to be done is very handy. I have the tests in groups; individual tests are subtasks of the higher up groups. I simply created fields I needed, like “test prerequisites,” “Test steps”, “test results,” et cetera. I can put in exploratory charters if I want or write things for other people to run.
One advantage of using Jira is everybody has access to it and there are no excuses when we say, “Hey, you team members need to run the following tests” – they can easily bring them up and follow the steps.
It’s not a fancy life, but it’s working.
3 Likes
@suuske1981 I completely understand where you coming from. I used to use TestRail. Found it very easy to import / export and manage tests. You can integrate it with jira and also with automated tests. I worked with Zephyr as well and found it much harder to maintain. Spent quite a bit of time evaluating the different tools and can recommend this one the most.
@suuske1981 having been a JIRA administrator for many years now, it isn’t the best tool for test management but if can be used in a TDD style very well, if you know how to create and customise Issue Types and have test resource that doesn’t rotate very much.
Keep it simple I’d say and rather than steps, as is traditionally suggested, I’d say that if you can use the Acceptance criteria in the User Story, do that and don’t create tests at all. If you do want reusable tests for others to execute, I’d say look at Zephyr or Xray as others have suggested.
1 Like
@cally6359 thank you for this.
I am using it for acceptance criteria in the User story. Have only a test case sub task so that the developer can put that task in the right column. And if needed that I can put some extra information in it.
Most of the times I am testing the projects via the agile testing way now.
So a lot of exploratory testing and automated testing.
1 Like