Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to create a Jira project for all testing and other QA activities? Edited

As Development, requirement management and Business requirement management use their own Jira projects. I'd like to set up a separate project for all kind of testing tasks across multiple IoT products (embedded SW). Test planning, preparation and execution on multiple test levels with multiple pre-condition shall be possible including test automation using xray robot framework integration. Any best practises or helpful documentation is heavily appreciated. 

May be there is a step by step approach outlining possible setup options and useful reports

1 answer

0 votes
Jack Community Leader Jan 14, 2021

This is more of a discussion since there is no best answer I suspect. First I question a bit not having testing within the project that defines each project. However, if I were to group all testing under a single project I would probably choose to use components as a means of identifying which product/project a TV was associated with. This could also be done using a custom select field. I am not experienced with X-ray so maybe others that are will add their input here. 

Thanks for the feedback. Testing within the same project on unit-, CI- and system-level makes sense if all parties are aligned in the same picture frame. Working with lots of different teams increases the risk, that a single project may not cover all teams demand. Especially a customer-oriented QA team may have additional acceptance criteria based on UX, KPIs, competion and special market risks, which are not fully covered by a scrum based development process. In addition several products might use common components and shared services (e.g. BLE, WiFi) which require a different QA-oriented view as opposed to a feature implementation for a specific device.

Browsing through Jira help I found this explanation of a Xray test set: 

"This is the Xray Test Set Issue Type. Creates a group of test cases. Used to associate all included Tests with other Xray issue types like Test Execution and Test Plan. A Test Set can also be associated with a requirement issue to provide coverage and test status."

The last sentence triggered my thought on using a separate project

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

215 views 1 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you