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

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? 

1 answer

1 accepted

@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.

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.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

147 views 1 17
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you