How can an admin set up a QA lead and assign it to a component? There is the component lead in which we set in to the lead developer, but how about a QA lead?
Yep, no way to do that on JIRA out of the box. May I suggest to separate your "Dev JIRA Project" to your "Test JIRA Project". This way, you will have "Project Dev Component A" for your "Project Test Component A"
There is now way to do this in JIRA. Can I ask how you're trying to leverage this, perhaps as a use-case?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Steven F Behnke our team needs this functionality and our use case is as follows:
Our workflow is such that the developer assigned to fix the issue should mark the issue Resolved and assign it to QA after the fix has been merged.
We want to further add an automated rule such that if the status of the ticket is "In Code Review", then when the PR is merged in Github, Jira transitions the status to "Resolved" and sets the assignee to the QA lead for the component. Currently there is no way to express "QA lead for the component".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I answered this initially about 5 years ago. It's probably best to open a new question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.