Jira
Sort by:
Trending
Status:
Showing 264
2
VOTE
Add Product Prefix field as a choice in the JIRA integration
We integrate Aha! with multiple JIRA projects and often use the product prefix as the Component to identify the source of the ticket. Today we use a constant and add that manually. Adding it from the prefix would save us a lot of time!
0
Future consideration
3
VOTE
2
VOTE
Allow for "approve incoming changes" in Jira integration
There is currently an option to approve outgoing changes or incoming records, but not incoming changes.
The current options are:
- Allow any Jira user to directly impact sensitive Aha roadmap information by changing Jira tickets (we map Epics to F...
0
Future consideration
3
VOTE
Link Features to Multiple JIRA Projects
This would be useful in sending features to more than a single JIRA project. Our development teams are organized around services and platforms and often end user product releases rely on multiple JIRA projects and teams. It would be ideal to link ...
0
Already exists
2
VOTE
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...
0
Unlikely to implement
2
VOTE
Integration Updates > Send Changes > Add Release filter & Status filter
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...
1
Unlikely to implement
1
VOTE
2
VOTE
Attachments linked to Note custom fields should be supported in Integrations 2.0
The note custom field allows for documents to be attached. However, when "attachments" are synchronized between Aha! and the development system, only attachments linked to the Description field are sent over. It would be ideal if the documents att...
0
Future consideration
1
VOTE
1
VOTE
Many to one mapping for field integrations
The use case for this is we have 7 different fields for grouping development teams containing over 50 total teams in Jira. We would like to be able to combine these into a single field in Aha for the purpose of running reports to show which of the...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved