How To Link Issue Board to DevOps Board?

[Geoffrey Williston]

I am working DevSecOps, and that team has it's own board for team issues, etc. There are also 3 developer teams working on their own Jira board with their own issues. 

Is it possible to create a separate fourth board, an "Issues Board", that the devs can navigate to and report bugs/request tools on, and have that "Issues Board" auto populate into the DevSecOps board backlog, so that the DevSecOps team can then use?

----------------------------------------------------------------------------------------------------

Edit for more information:

Dev teams who don't have permissions to access the DevSecOps team board can't add issues to the DevSecOps board - but they would be able to add issues to the Issue Board. In turn, these issues from the Issue Board would auto-populate into the DevSecOps team backlog - but the DevSecOps team could move items into sprint iterations at their own discretion (if the item has a low priority, it stays in the backlog, etc.)

The overall question: Is it possible to link two separate Jira boards, so that when one issue is added to a board, it is auto populated into the other's backlog? If so, how?

[Craig Nodwell · Accepted solution]

Hi @Geoffrey Williston welcome to the community.  You can make as many boards as you need.  Providing the issues they create are going to the DevSecOps project it will show in that boards backlog. 

[Geoffrey Williston]

@Craig Nodwell Thanks Craig! My question is, when I make this separate Issue Board, how can I link the two - so that an issue raised by the team in the Issue Board also auto populates in the DevSecOps team specific board? 

Dev teams who don't have permissions to access the DevSecOps team board can't add issues to the DevSecOps board - but they would be able to add issues to the Issue Board. In turn, these issues from the Issue Board would auto-populate into the DevSecOps team backlog - but the DevSecOps team could move items into sprint iterations at their own discretion (if the item has a low priority, it stays in the backlog, etc.)

[Craig Nodwell]

I'd think the easiest way to handle this would be to have the issues created in their own respective projects and assign the issue to a member of the DevSecOps Team then base your filter in the DevSecOps board to pull issues assigned to any team member.  

[Geoffrey Williston]

Thanks for your insight @Craig Nodwell 

[Craig Nodwell]

Note: this is how I handle this type of thing now for both our DevOps and Production Support teams.  Issues can be raised in any project for those activates, but the filter on the Boards that those teams work off of are based on a group membership re:
assignee in membersOf("DevOps").  That's on a DC instance you may not have this in cloud but you could just simply build it up re: assignee in(person1,person2,person3,etc)