Add option to show additional columns/fields in "Integration updates" window for Jira
The "Integration updates" window currently only shows the issue summary of incoming issues. Presumably the JSON payload being received by Aha contains the full set of information for the incoming issue ... it would be incredibly valuable to be abl...
Gene Lewin
about 1 year ago
in Jira
0
Future consideration
Azure DevOps integration support for designating default Iteration as backlog
Currently the Azure DevOps Services integration supports configuration of the project and the project area. All work items go to the root project iteration level. However, multiple teams may work in a single project and have a different iteration ...
I am building a bot for Aha. I want to go to a channel and say: > @aha subscribe PRODUCT_ID> This channel will now receive updates made to PRODUCT NAME
On the backend, I want to create an activity webhook with a highly custom webhook URL. Ri...
Byrne Reese
over 5 years ago
in Integrations
1
Future consideration
Update mapped initiative field in integration when changing text of initiative name
The initiative field is available in the Jira integration under the Aha! feature record. It works as expected when initially sending the Aha! feature to Jira. (Note: this is not the use case of mapping the initiative record.) However, the mapped i...
Craig Pflumm
over 4 years ago
in Integrations
0
Future consideration
We create UX/UI mock-ups in Aha!, and I would likedevelopers to be able to see them after the feature is pushed into their Jira backlog. I noticed that both Aha! and Jira use Draw.io for mockups. Is there any way Aha! can upload mock-ups associate...
Guest
over 5 years ago
in Jira
4
Future consideration
Apply "Update records" to a subset of records in an integration
The "Update records" function is very useful when Aha! Roadmaps becomes out of sync with my development tool- I can use it to bulk-update all of my linked records to make sure they are up to date with Jira. But, there is risk inherent in this kind...
Reilly O'Connor
over 2 years ago
in Integrations
0
Future consideration
Integrations 2.0: JIRA Default map Aha! URL to JIRA Aha! Reference field
1.0 did this; 2.0 does not.
As a user I have to manually add the mapping between the URL field for an Aha! record and the Aha! Reference field for the JIRA record.
For Releases we automatically map the URL to the description field.
For Features/...
Danny Archer
almost 7 years ago
in Integrations
0
Will not implement
Limit workspace users choice to 1 user instead of multiple (like the Assigned to) field
I need to add the workspace users as a custom field in my template and currently it doesn't limit to just one user, it allows multiple users which I cannot have. Can we have an option to make it a single choice only. in the attached graphic is the...