"Best workflow" would be different in different situations. In some teams it's enough to have Todo->In Progress->Done workflow, in other teams you'd have dozens of statuses.
If you need this answer to set up the most fitting workflow for your team, could you provide a little more context? What type of projects (products) are we talking about, what is a typical lifecycle and lifespan of a product, how many products do you have, how many features may a product have, are products more or less similar? What are the roles involved in working on the product in your company, what is the methodology or practices used? Is customer involved, do they have access to your JIRA?
I can list more and more questions... The more information you provide, the more useful an answer would be.
By the way, this is what typically is done by a consultant that comes to your company and designs the best way to set up JIRA for your processes. If you're not sure about how to proceed, you might look into contracting someone to do this for you -- could be cheaper, all costs considered.
Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...
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!
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