I am the QA lead for a company that has multiple teams with their own projects in Jira. Is there a way I could track Jira tickets from for example, the engineering board or bug board in the QA board so I can assign those features/bugs to QA team members to test?
1° you need the right authorization en each project
==> comment ? edit ? view ? assign ?
you jira admin as many way to do it.
==> create a "QALead" rôle ==> give each needed authorization to this role in auth scheme of each project ==> give this role to your account in each project
2° with this you have now an access to the issues ticket. You need to select the right selection of ticket
Create a filter.
How did you recognize wich issue in each project is for you ?
Let discuss with other members of teams ;) Why not by a tag or a status in workflow ?
3° create a board to let it more readable. Base your board on the filter.
Short version: yes.
Jira is based in 3 key concepts that new users oftentimes struggle to understand:
To illustrate this, I like the library analogy:
- Each project is a library.
- Each book in this library is a card.
- Each shelf is a board.
You have different libraries: math, history, geography, philosophy, physics, chemistry.
Here comes the tricky part: the shelf is dynamic and can show any book you want - from any library - although it's physically "appearing" inside one single library.
So, you can have a "XXI knowledge shelf" inside any library. It could (if you want and configure accordingly) show math, history, physics, all at once.
Likewise, you could have a "Newton shelf" and it would bring items from physics, philosophy and chemistry libraries.
Still, the books are unique and belong to a single library. It means that if someone using the "Newton shelf" writes a note into Optiks book, someone looking at this same book in the "XVII knowledge" shelf would see the note.
Books and libraries are unique. Shelves are "views" on top of these books and libraries.
Back to your case:
You just mention boards and that each team has a project. It's implicit whether "team" is QA team or Alpha team composed of QA + Engineering. Hope the analogy above helps you to adjust it to your reality whichever it is.