Update the JIRA sprint field with better import

Currently if a story has belonged to more than one sprint, the sprint field concatenates the sprint.


For example, a story was in sprint 2019.5 and then moved to 2019.16 and then moved to unscheduled. In JIRA the story is none +2 indicating that it is currently not scheduled, but was twice previously. In Aha!, the custom field is 2019.15, 2019.16 - that is not both tags, that is a new tag created. This elongates the list of values for sprints and makes it unusable for reporting.


The sprint field in JIRA does not allow commas, so it would be great if you could read the comma and understand that there is more than one value or if JIRA allows you to see the current sprint in the API and not the past.

  • K Wollery
  • Aug 29 2019
  • Already exists
Release time frame
  • Attach files
  • Admin
    Austin Merritt commented
    September 03, 2019 17:47

    Hi there! Thank you for reaching out about this. I tested this and asked our customer success team to take a look as well. We are not able to reproduce the issue you are seeing. When a story is moved to a new sprint in Jira, a new sprint tag is created in Aha!

    Can you please send an email to support@aha.io with more details about the steps you are taking? They can help you get to the bottom of the issue. Thanks!

  • K Wollery commented
    September 04, 2019 18:14

    It happens on the initial import. The import does not separate the values of the sprint by the comma and JIRA retains a history so all of the sprints concatenate into one tag

  • Admin
    Austin Merritt commented
    September 04, 2019 21:56

    Thanks for clarifying. I tried importing as well and also was not able to reproduce this. That said, I may be misunderstanding how the story is being updated in Jira before it is imported into Aha! I have asked our customer success team to follow up with you directly to help out here. Thanks!