Don't Write Separate Stories/Tickets Just for Testing
In general, if you're using Jira (or any ticketing system) to drive task-level details, then you aren't really doing agile user stories. Instead, your routine testing tasks should be part of your "Definition of Done" for testing, and you may not even need testing-specific stories.
In pull-based work queues, testers should pull a user story into the testing stream whenever it's been marked ready by the developers. Standard tests and implicit elements of the Definition of Done are then performed, and any checklists or documentation that needs to be attached to the ticket can be added as a file attachment or linked in the ticket's notes section.
I strongly discourage teams from having separate testing stories because they are not separate features. Rather, testing is an intrinsic part of ensuring that a feature is done, and any feature that is tested or that fails testing is not-done.