We are using JIRA and GH with a custom workflow. The assignee field is used to indicate which developer works on the task. Once the development is complete, they move the issue to a custom status of "Requires Testing," at which point the QA team picks the issue up and tests against it. This follows our team's definition of done, however because it is in a status with no resolution, the issue still appears as open in the JIRA reports. As a workaround, we added a resolution status of "Requires Testing," which closes the issue.

We've added a custom field for "QA Assignee" to track who on the QA team will test against the issue. In order to edit the issue, QA must re-open it, then edit the assignee.

There are two issues here: the first is that the "assignee" field is limited to one user. I would like to have the ability to have a development assignee and a QA assignee, and maintain the user selected for each one for the duration of the issue (for auditing purposes). What would make sense would be the ability to configure multiple assignee fields in an issue and select the assignee from defined project roles.

The second issue is that we have developed a cumbersome workaround for flagging the issue as being ready for QA. If we leave it in the custom status, the issue appears as Open and the charts don't track correctly. If we set it as Closed, it disappears from the reports and shows them as closed, but they have to be re-opened to assign the QA assignee. I would like to be able to configure the definition of done - ie) if the status is "Requires Test" but is unresolved, configure this as done - it would allow us to avoid a step of having to resolve the issue for reports and then re-open it to assign a QA tester.