Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT

The note in the idea descriptions that the PMs are forced to work in Jira instead of Aha should be red flag for Aha leadership. The goal should be to allow the PM to work in Aha as much as possible. Once they are working in Jira or in our case TFS instead, it makes it move difficult to keep the enthusiasm for Aha. Bouncing between applications sucks.

Can you please give us an update regarding the ETA? Are you still planning to deliver it as mentioned above?

This is really annoying for us and requires a lot of manual work... Thanks

 This is the single most annoying issue we have. Why cannot I not map a sprint in Jira to Aha. Would be even better to link Release to Sprint, but I'd settle for a custom Aha Sprint field to sync to Jira. Please fix this!!

This is basically the missing piece that is keeping the majority of my PMs from using Aha to manage their features and planning effectively.  It is a lot of manual work to keep weeks / sprints in sync on the planner, so much so that we wrote a script to tell us where it is out of sync.  Being able to add and sync features into JIRA sprints as stories would be massive using Integration 2.0.

For us, this is as much about reporting and notebook views for project managers and dev leads as pushing features/requirements in a sensible way to sprints. The more people in the organization who can recognize their contributions (in their terms) toward goals in shared presentations, the more influence my product team has to drive company and user agendas. Thanks for proposing this idea!

Why are we yelling sprint and Jira?  I get that we all want this feature... but let's calm down a bit ;)

Why not use master features as features, features as epics and requirements as stories?

engineers can then own the epics and stories which will deliver the feature. Especially relevant if multiple engineering teams required to deliver the feature.

@Doug Surrett I do the same (or something similar) to fit with our monthly release cycle, but then I have to create a Company level release above the product level release sprints to tie everything together. Makes things more complex but works...

This feature will ease -  the process so much. Now it is a pain

We are using release phases to assign features to sprints. If we could map a release phase to a sprint, this would solve the problem for us.

This feature is likely what will convince myself and our team to adopt Aha. It's the one capability that I have been desperately trying to solve in Aha and I haven't been able to. How soon will we see this? 

Also needs to integrate with Rally

This would be great especially with two way sync as Sprint planning will move tickets from one sprint to another.

Please also enable this for TFS

As I'm using Aha scorecards to prioritize features, this is crucial to be able to then use the data of Aha score to then sort features into sprints in Jira. Without this or the ability to send Aha score to Jira, the Aha score is useless for my team.

This is absolutely needed for Aha/Jira integration to work.

We are looking for a feature that helps me map a release template phases
to sprint(s) in JIRA, so i can assign to-dos I need to fulfill to a
certain Aha release phase to a JIRA sprint, and assign that to a person
- eg. I would raise architecture decisions we need to make as
to-dos, map them to a pre-development release phase, and assign them to
be completed by someone _before_ we start the development phase on a
feature.

This would be a great addition to the tool. I wish I could give it many votes. 

I just added another item that I think would work very well in conjunction with this feature. Read about it here.

https://big.ideas.aha.io/ideas/APP-I-3106

Upvote it along with this one.. the two ideas would be very complimentary.