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

Accepted Answer
1 vote

@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
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

454 views 7 5
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