Creating an issue in project A views, but actually creates an issue in project B

[Mike Hirons]

Hi all,

I'm designing a new Jira structure for the organisation. Ideally, I would like to achieve this:

The QA team has their own project space, that does not contain any issues (bar some misc admin, and CI things).

The QA team's project space is populated with boards, with each board representing a development project that the QA team is supporting.

I know I can achieve this through smart filtering/board setup etc.

What I'm struggling with, is an easy and elegant way for a member of the QA team to raise an issue, that will belong in the 'true' development project, but while they are viewing the boards.

I'd like this, so that the QA team working on testing the development project (usually multiple heads, working on multiple projects at a time), can operate from single, clean and controlled space/interface.

I know that I could create an automation task, that could duplicate and delete - but that wouldn't accommodate unique fields/components etc from the 'true' development project, without a lot of bespoke automation for each and every development project.

Has anyone tried anything similar, and has been able to come up with an elegant solution? Am open to suggestions, even if it takes away from using boards like this.

Am also open to team or personal boards (pulling multiple projects into one board - but being able to create an issue that will be created in the development projects).

Any thoughts?

[Mike Hirons]

If this isn't possible, is it going to require a custom/script runner solution?