JIRA/Stash/et. al isn't so bad, but I definitely prefer using GitHub Issues or Trello for my own projects. ZenHub looks pretty cool too. Definitely think the way that we use JIRA at my office is the only way to use it "right", in the sense that we basically track everything with JIRA tickets, from IT maintenance requests to operations bugs and project management tasks. The automation between JIRA and Stash is also 10% awesome, with that other 10% lost because you can't specify a code reviewer in a Stash pull request and have that person be automatically assigned to the JIRA ticket you're working on in the branch. Little failures like this are commonplace among the Atlassian toolset, which is why I don't like using it quite as much.
I'm a product manager for Stash, and was curious about your expected Stash/JIRA workflow. Why would a reviewer be assigned to the JIRA ticket? They're assigned to the pull request for the issue that the author is assigned to (who did the work). Are you wanting to have a JIRA-only view of work that needs doing, including review?
