@jslawinski, your offer was discussed at the dev call yesterday. The main take away is that people are excited about Soldevelo taking a lead on this and you guys have the green light!
Please let us know whenever you are ready to start.
I went through the docs you provided and this guide on setting up JIRA for QA was particularly interesting: https://confluence.atlassian.com/display/JIRAKB/Customise+JIRA+For+Test+Case+Management
The user guide at the bottom of that page gives a good insight in how the workflow could look like:
A new test case is defined by creating a new TestCase issue in Jira and filling in the required fields such as Summary, Description and Component. For each release where this test is going to be run, a subtask of the issue is created and the Affects Version field is set to the release. The priority of the test for this release can also be added here. Use assignee as the person who defines the test.
When a test is run, the results are entered or updated in the subtask, not in the parent Test Case issue. Comments about the test run can also be entered if appropriate.
When a report is created for the current state of a release, we search for all TestCase issues with the Affects Version field set to the required release. The resulting set of issues can then be sorted and counted by number passed, failed, not run etc. Producing historical reports can be done with the Timecharts plugin for Jira, which shows a graph of how the results in a report change over time.
We can also create a new link type to connect test cases to the bugs that they created or are verifying. This is the biggest advantage that I see of using an issue tracker to track test cases and bugs together. We could also add a box to all bugs to indicate whether a Test Case is expected by someone for a bug.
I do think it would work for us. I understand you used some variation of that for MIFOS. I haven’t found any issues with subtasks, but this query gives some examples of test cases https://mifosforge.jira.com/browse/MIFOSTEST-1198?jql=issuetype%20%3D%20"Test%20Case"