This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
Ryan Schultz
over 9 years ago
in Jira
0
Already exists
Prevent feature workflow from moving if a feature is in JIRA already
If the feature taskflow is aligned with the status of features in JIRA, the status of the feature will automatically update in Aha as the feature progresses through the development phase; this is good. What's problematic though is the user can adj...
Dale Burnett
over 9 years ago
in Features / Jira
0
Will not implement
JIRA came first at our company, and only a handful of users use Aha -- consequently, when I publish a roadmap, it is assumed that the issue numbers shown on the roadmap are JIRA issue numbers -- this creates a lot of confusion. I would like to be ...
Cameron O'Rourke
over 9 years ago
in Jira
2
Unlikely to implement
Allow users to refresh all Aha! features from a linked JIRA integration.
Currently, only the changes made to a JIRA issue are sent over to Aha! through the webhooks. We should have a way to force Aha! to synchronize all descriptions and fields from JIRA for an entire release.
Alex Bartlow
over 9 years ago
in Jira
0
Already exists
Hi Guys
We have mutiple JIRA to single Aha! product, so when sending we see the image attached. You cannot distinguish which JIRA in this list - please extend to: Send to JIRA: VIS - where VIS is the name of the JIRA project. Seems a simple quic...
Andrew Tipton
over 9 years ago
in Jira
2
Already exists
Allow tracking simultaneous tracking of both Feature-Level and By-Requirement estimates
The current AHA/JIRA estimate integration allows feature level OR requirement level estimates, however as we don't use JIRA for time tracking we want to use JIRAs 'Original Estimate' field with AHA's per-requirement estimates.
My suggestion would ...
Guest
over 9 years ago
in Jira
0
Unlikely to implement
Pull JIRA Original Estimate not Remaining Estimate
We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...
An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix versio...
Danny Archer
over 9 years ago
in Jira
17
Future consideration
Assignee does not get sent to Jira if using Default Assignee functionality
If you use the "default assignee" functionality, then that assignee will not get sent to Jira, even if that user exists in Jira. This could be considered a bug.
Avigail Ehrenhaus
over 9 years ago
in Jira
0
Already exists