Plus 1 for Aha integration. They have their own story mapping now, and if it weren't for the fact that storiesonboard is easier - we would be using it in Aha. We use Aha for our product planning, so this integration would be important to us.

Aha has now released its own story mapping capabilities: https://blog.aha.io/user-story-mapping-tool/

If you don't add support for Aha and stay ahead of the curve, they'll fill it. Story mapping is one of their post popular issues -- top 20 in the past year and continues to rank higher. Their integration service makes it easy to do, especially given you've already built a framework internally to support something as complicated as Atlassian JIRA.

Story mapping is a natural fit to link point-by-point new features and/or feature improvements back to 'master' feature/function capabilities. It's the missing link.

I'd also love Teamwork.com integration so i can get tasks going against things there. its much cheaper than Aha, and the tools i work with are based on my client's choice. sometimes aha, sometimes teamwork/asana.

to be honest - right now its never trello (as the task management reminders are really important in a remote team collaboration).

none of my clients have asked for pivotal tracker
And my use of the StoriesOnBoard board never directly translates to what i want to go into Jira or Github issues - because i use it to create a shared story/understanding with the client dynamically in workshops... that i then need to spend some time working on to get it to a stage the developers would be vaguely happy to accept as a release.

+1 for Aha!

Aha! please

+1 for Aha!

Thanks for the question Keji! Which one would you be interested in? I'd turn this idea to a feature request for that.