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).
Unless...
Guest
over 5 years ago
in Jira
0
Future consideration
Persistent filters for integrations and incoming product updates
Using JIRA integrations, I have an Aha product that spans several JIRA projects. To work with this I have set up an integration per project with a specified JQL filter. For example my filter could include "priority = high". Other products througho...
Guest
over 5 years ago
in Jira
0
Future consideration
Merge Custom Fields into One Field when they are carried over from Idea to Feature
At idea stage you capture information about the idea in multiple fields, when you promote this to a feature if this information was merged into one 'Body' field, then I would save time not having to copy and paste those fields into one field.
Ha...
Guest
over 5 years ago
in Jira
0
Unlikely to implement
Feature Email update notification to include link direct to Jira record
From a time saving point of view it would be really handy to include the Jira link in the email notification that comes when an item is updated. This field/link already exists within the feature itself so should be easy enough to add in to the ema...
Scott C
over 5 years ago
in Jira
0
Future consideration
We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase
Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key t...
David Vins
over 5 years ago
in Jira
8
Future consideration
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
almost 6 years ago
in Jira
1
Already exists
JIRA integration: support mapping of “Release name” into custom field
Mapping of “Release name” towards custom fields in JIRA integration instead of “fixed version” or “affected version” only
currently the AHA-Jira integration only allows a mapping of "release name" values in either "fix version" or "affects versio...
Florian Kette
almost 6 years ago
in Jira
1
Unlikely to implement
On the Aha! Integration Updates screen for an Aha! to/from Jira Integration, I would like to see which releases and the status of what each of the items are for integration. Being offered these filters would allow me to select that before importin...
Guest
almost 6 years ago
in Jira
1
Unlikely to implement
Aha should support multiple "types" in Jira (epic, bug, use case, tasks) in one single Aha query
Hortonworks uses following Types in Jira application: Epic, New feature, PRD, Tasks, Doc.
Currently, we have to create multiple queries using Development tool in order to bring the above Jira tickets to Aha.
Requirement: The query should bring a...
Guest
almost 6 years ago
in Jira
0
Unlikely to implement