A separate project for non-technical bug reports and requests?

Ingrid Hartman

Right now our team has a entirely separate project called "REQ" which the entire non-technical staff uses to create bugs, feature requests and tasks. Then my job as a PM is to go through, validate bugs and feature requests, and move them to the real WEB board, where they get prioritized and put into the sprint.

I feel like this a weird system and we might be better served by having a single board and then just having a workflow step to validate things before they get put on a dev board.

What are people's thoughts? Does anyone else have a similar setup? 

Meck

@Ingrid Hartman,

Your actual way works, but the best way is use one project with a good workflow. The workflows are such powerful at JIRA, you can do a lot of things with it.

• https://confluence.atlassian.com/adminjiraserver071/advanced-workflow-configuration-802592741.html
• https://confluence.atlassian.com/adminjiraserver070/working-with-workflows-749383109.html

I think the better way is your idea have a single board and then just having a workflow step to validate things before they get put on a dev board.

Regards.