You're not the only one with this issue. We don't have the ability to update test executions and assign these ad-hoc executions to test cycles. I don't like this feature either and think that all test executions should only be executable if assigned to a test cycle, but there's no way around it that I'm aware of. Fortunately, in my projects I have come across this issue very rarely
Thanks for confirming that. Unfortunately for us we often get inexperienced users starting execution of a test via the linked Jira ticket, not from the Test Cycle. Extremely frustrating not being able to add a Test Cycle after the fact, or delete adhoc executions that haven't yet been started.
