Thank you for providing the reuiqrements. Please let me address each one in turn for possible ways to implement it in JIRA:
> In a defect provide a link to a test case the defect was found under (this helps verify you have coverage for bugs as well in your test plan, and helps the evelopers
> who are looking at the bug understand the scenario clearly. No need to mention generic steps and descriptions of scenarios when referring to a known test case)
As far as I can tell the the test cases are kept in an external system which is accessible with a web browser. If so, the link can be provided in a URL Custom Field. The custom field can be setup to appear only for defect (bug) issues, for example. For more information on custom fields please see:
Also, please note that JIRA will automatically detect hyperlinks in all long text fields, so the links can be simply inserted in the description of the issue or in a free text custom field.
> In a feature or other issue type provide a link to a test case the defect should be veified under (again helps with coverage).
That can be another URL Custom Field (called e.g. Verified Test Case) or another simply link in a text field.
> In a defect provide a link to a test run result that caused the defect. This provides a pointer to more information about the scenario of the bug,
> the test results, logs, etc.
> For a test case / test script provide a link to a feature/bug/other issue which is blocking that test case. (dependencies). This allows reporting what percentage of the > test plan is blocked by open issues.
If a test case is actually an issue in JIRA, Issue Linking can be used to represent dependencies. For more information on issue linking please see:
It is then possible to build custom workflow conditions to e.g. restrict resolution of issues while dependent issues are still open. Custom reports can also be built to show the dependency graph of issues. While these conditions and reports are not shipped with JIRA at the moment, information about how to implement them can be found here:
> Notify upon test plans that become unblocked since bugs have been resolved.
In JIRA the easiest way to notify people or external system is to create a Listener that will od the required work on a particulr reports. Listeners are described here:
Please let me know what you think about the above.
Building all of these as a single plugin for JIRA would be very cool indeed. However, given our current work load it might be some time until we will be able to make this plugin a reality. I hope that JIRA already exposes all the right hooks for the integration to be built. Of course, you are more than welcome to implement this integration in-house.