Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features
Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter
about 5 years ago
in Jira
0
Future consideration
Maybe this more of a product idea for Prezi team, but it would be very cool to be able to embed Aha! views and notebooks within a Prezi. Maybe there is already? The business value would be able to convey complex visual concepts (prezi) mixed with ...
Guest
over 7 years ago
in Wanted
0
Will not implement
Parent version mapped to 2 different releases - let user decide where to import
The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe
about 5 years ago
in Jira
0
Future consideration
Features should Inherit initiatives from Release & Master Release so all Pivotal stories are under the Epic after sending to PT (and the Epic is actually created)
When pushing a feature to Pivotal Tracker, a user can select a mapping that allows for initiatives to be mapped to epics. The only initiatives this works for are initiatives directly referenced by a Feature. Any initiatives referenced by the Relea...
Guest
over 10 years ago
in Pivotal Tracker
7
Unlikely to implement
Automate service account password updates for TFS integrations
Right now we have a TFS integration configured with Aha which requires us to use an AD service account for TFS. This service account password needs to be manually added within Aha! however we have a policy that all our service accounts require pas...
We use the slack integration for PMs to know what each other is up to. It would be great to see the Product name as we change other details for each initiative. This makes it clear what product is changing.
Ken DeBlois
almost 8 years ago
in Slack
0
Future consideration
Slack to Aha integration - option to make actions visible in the channel
It would be very useful if others in the Slack channel could see that an idea / feature / etc. was added, so that they could vote on it and maybe add their own perspective.
At the moment, the confirmation that the idea was added is only visible to...
Guest
almost 8 years ago
in Slack
1
Future consideration
Provide applicable error message when a Jira integration can't authenticate due to a captcha challenge issue
When attempting to set up a Jira integration, authentication can fail with a 403: CAPTCHA_CHALLENGE error we can see in the logs, but there is no applicable message on the integration-set up screen. It just says "We could not connect to your Jira ...
Emily Yankush
over 2 years ago
in Jira
0
Future consideration
At the moment, for the JIRA integration the JIRA account used to connect must have admin rights. This doesn't work for our security protocols because that would mean we're opening up access to secure projects that live in the same JIRA instance th...