The biggest problem I see with requirments, once they are written down and something changes, they are not kept up to date, thats why actually I like having the Requirements in Qase, as there I can link them to testcase and define the testcase accordingly. And Jira than is only responsible to host the implementation issues. So a cool feature for me would be: define the requirement in Qase and export it into a Story in Jira, introduce the review process for Requirements like you have it for testcases Automatically update the requirement in qase if the jira story is changed -> init the review process