We've recently started using capture for JIRA for our testing, however we've encountered an issue where we only seem to be able to add related issues from one project into a test session.
As I am in a multidisciplinary team, we have a JIRA project for each discipline (software, mechanical, electrical, etc) as they often have different workflows/sprint lengths, but we are often testing related issues from multiple projects in one session.
At the moment the only way you can do this seems to be by moving the issues to one project, adding them to the session and then moving them back. However this isn't a real solution as it breaks workflows, sprints, etc. And it also means you can't edit the test session once you've moved it back.
Thanks in advanance for any tips on how to get round this!
Hi Harry J.E Day,
In Capture, test sessions are bound to the project. Therefore all the issues that are reported in the test session are reported in the correspondent project.
Transitioning issues sounds like a bit of a hassle, yet since all the issues are reported in the same project - you either need to transition or clone these issues (latter would require transitioning to the correspondent project too). When you clone - issues can be cross-linked so it simplifies the navigation.
You can consider using smaller & focused test sessions for each project. If you need engineers from other departments (projects) to participate - you would just invite them to the session too. This way you would need to transition only few issues to the correspondent project.
JIRA Developer at Atlassian.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot