Default workspace name filter in integration updates screen
In order to limit the information displayed in the integration updates screen to be more relevant, set the workspace name filter to default to the workspace chosen in the application rather than defaulting to show all
Keith Davenport
over 3 years ago
in Integrations
0
Future consideration
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
almost 10 years ago
in Pivotal Tracker
0
Will not implement
Import functionality to show the entire list of records and have ability to import only selected (check box) records
Currently Rally import functionality shows only top 10 records extracted for the set criteria. Want the ability to see all the records with checkbox to allow 'pick & choose' for import Do not show the records which were already imported or linked
Jyothirmayi Talaparthy
about 5 years ago
in Rally
3
Future consideration
Allow custom integrations to behave like built-in Integration 2.0
Who would benefit? Companies that use dev tools that aren't supported by Aha! What impact would it make? Removes lots of manual work and improves UX for custom integrations. How should it work? Allow adding custom integration with a name and icon....
Alexey Zimarev
over 1 year ago
in Integrations
0
Future consideration
Currently JIRA webhooks function globally which means we cannot have separate webhooks with filters from multiple Aha workspaces to one shared JIRA project. In this use case there is a large offshore team that is shared by several products within ...
Guest
over 3 years ago
in Jira
0
Future consideration
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
over 6 years ago
in Integrations
0
Future consideration
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 7 years ago
in Jira
0
Future consideration
Jira Integrations: Map Aha Releases to a custom Jira Version Field
Who would benefit? Any Aha customer with jira integration that uses a separate jira field that has version data as values to enter. In my jira project I use a different field (other than fix version) to track what release our features will release...
Kyle Shannon
over 1 year ago
in Jira
0
Future consideration
Who would benefit? Anyone with a GitHub Integration What impact would it make? Right now, the syncing of an Aha! Item Requirement's tag is not supported. This means any requirement that the visibility of tags on a requirement is lost in GitHub if ...
Guest
over 1 year ago
in GitHub
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 7 years ago
in Pivotal Tracker
1
Will not implement