Using Jira for Bug and Test Case / Plan Management

[Javier Ortiz Bultron]

I'm trying to continue this thread: http://forums.atlassian.com/thread.jspa?messageID=257253472

I have some questions about the Use Guide at the end of this article: http://confluence.atlassian.com/display/CONFEVAL/Customise+JIRA+For+Test+Case+Management

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.

I'm havin gissues in figuring out how to actually do that. From what I understood, the test cases are emant to stay in the template status and creating Sub-Tasks from it. If I got it write that will create a new instance at the start of the workflow instead of continuing where the parent was.

The only way I got to link them to the parent was then turning them into Sub Tasks which allows it to be linked to a parent.

Any help?

[Javier Ortiz Bultron · Accepted solution]

Not straight forward. I'm moving away from this option. I'm looking at TestLink and possibly creating plugins to enhance its current integration. Hopefully time permits.

I already started on the NetBeans side with plugins: http://plugins.netbeans.org/plugin/39489/?show=true

[Javier Ortiz Bultron]

I believe this is a gap that Atlassian needs to fill soon. It is the missing piece on their suite of tools. Either implementing their own, buying and then integrating an existing one, or greatly integrate with an already available one.

[Joel Johnson]

Not exactly an Answer, however, I am doing something very similar.

I followed the exact steps and that particular step had me stumped. It Appears that you have to Clone the issue and set the status and affectes version then, creating a sub task actually starts a sub task issue type , and it does not inherit the same workflow from the parent issue.