RELATED IDEAS
Include comments when importing from Jira
When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jira comments when importing into Aha.
| Release time frame | 3 months |
-
ADMIN RESPONSEOct 3, 2024
We recently released an update to our Jira integration.
This change will import all comments for imported records via the "Integration updates" modal or the "Import from integration" workflow.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +2
1
MERGED
1
MERGED
BUG: Comments from Aha! Epics not transferred over to JIRA integration
BUG: Comments from Aha! Epics not transferred over to JIRA integration Comments, and information in those discussions, made in Aha are lost, even though there is a mapping field for comments when integrating Aha with JIRA
1
Shipped
8
MERGED
Import existing comments from Jira into Aha!
We have many comments in Jira which we would lose if they’re not migrated over to Aha! since these were created prior to the Jira 2.0 integration.So we are looking for suggestions on how to get comments created prior to the Jira integration mapped...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
I agree that this is a significant functional gap and hope to see it adressed soon.
In the meantime, for anyone else experiencing this problem I have a somewhat tedious workaround that has worked for me.
In Aha!, create your integration with Jira and import the records into Aha!.
In Aha!, create list of features with Aha! Reference IDs and Jira Keys. Export to CSV.
In Jira, create a filter that includes the issues you want to source comments from (you are limited to 1000 records so batch them if necessary), Export to CSV (all fields). (Excel export feature does not support comment fields)
In Excel, remove extraneous fields from the Jira Export (everything except the Jira key and comment fields). Note: there will likely be multiple comment fields, I renamed the columns to Comment1, Comment2, ... (up to the max number of comments on any issue)
In Excel, copy the Aha! Crosswalk export into a separate worksheet, in the Jira worksheet add a column to lookup the Aha! match to the Jira record (I use XLOOKUP).
In Excel, Save the Jira worksheet as a new CSV file.
In Aha! Import the new CSV file, mapping the Aha! Reference ID and ONLY ONE of the comment columns, then import.
Repeat step 7 for each comment column.
Repeat steps 3-8 for each additional Jira batch.
Good luck and be careful, it is easy to re-import the same column twice or forget to map the Aha! ID each time, resulting in errors, duplicate comments or features.
This is HIGHLY desired behavior. It's part of the mapping because it's essential. I can't understand why when you do the initial import it would fail. definitely need to fix this!!
I find it strange this isn't supported. I want comment syncing. Not sometimes comments syncing.
Existing comments are an essential part of the documentation trail for requirements that should be imported into Aha!. Failure to capture that information limits the ability to migrate existing requirements data in its entirety, thus limiting the (desired) ability to migrate requirements management entirely to Aha!
This is a "Must Have" feature.
We use comments in Jira to store the result of requirements discussions etc so to not be able to import them is a pain. Aha! must view comments as useful otherwise Aha! wouldn’t have provided their comment feature and provided a comment sync feature.