Be able to bulk update only rank or a single field within JIRA integration
Normally our product managers works on Initiatives in Aha! by editing/ranking them. Those field changes and ranking will sync to Jira backlog for architect team to work on follow priority of Initiatives. When a rank is changed for a record in Aha!...
Guest
almost 6 years ago
in Integrations
0
Future consideration
Integrate existing FogBugz cases into Aha! as features (similar to JIRA 2way integration)
This will allow teams that use FogBugz to onboard to Aha! easier, without having to orphan FogBugz cases already entered that cannot speak back to Aha! through the current FogBugz integration.
amy kennedy
almost 9 years ago
in Integrations
2
Unlikely to implement
Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date). U...
Guest
almost 6 years ago
in Jira
0
Future consideration
Link Aha! feature to an already existing pivotal story
It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.
Guest
almost 6 years ago
in Pivotal Tracker
1
Will not implement
Allow parking lot features and releases to not be sent to Jira
I use the parking lot to prepare for my upcoming releases thus the release name is not in Jira. These are also stories that do not need to be in Jira yet. With integration turned on I get an error every time I move a feature around in the parking ...
Kyle Cain
about 6 years ago
in Jira
1
Already exists
When I move a feature to the parking lot in Aha, it should move to the icebox if it exists in Pivotal
Most sprints priorities will change a little bit as time goes on and it will be appropriate to remove a ticket that was added previously. Likewise, if a sprint is over subscribed some tickets may roll over into the next sprint.
When this happens, ...
Jason Novek
about 9 years ago
in Pivotal Tracker
0
Will not implement
Allow Mapping of Requirement Type from Jira to Aha!
Presently, you can map types for items at the Feature level and this syncs between Jira and Aha! without issue if the item type changes in Jira; However, the issue that we are facing is that because there's no mapping between Jira and Aha! for req...
I R
over 1 year ago
in Jira
0
Future consideration
Allowing the ability to modify the status of a feature from Slack can be very useful when discussing features with DEV and Product teams to quickly update the move a feature from one status to another
Chris Stocker
about 6 years ago
in Slack
0
Future consideration
I'd like to build a slick integration between Hornbill and Aha!. Similar to the integrations you already have for Zendesk and Salesforce - we're looking to be able to create or update Ideas from Hornbill workflows, and to have Aha! provide Idea st...
Guest
about 6 years ago
in Wanted
1
Unlikely to implement