We have monthly releases configured. At the end of month, I move any open stories to the next month. The story reflects the new release, however, the associated JIRA ticket still shows the original release. To resolve, I have to go into the story, click "Actions" then Update the Verified Production Issues, within JIRA. When moving many stories to the next release, this becomes to time consuming.
Example: Tickets expected to be resolved in the month of July, are assigned to the July release. If the issue is not resolved in July, I will move them (ship it) to the August release. After "ship it" to August, the story in Aha reflects the August release, however the associated JIRA ticket still reflects the July release. This needs to be an automated process.
|Release time frame|
Thank you for the note. The current experience should work as you describe it -- as release information on features should get automatically updated in JIRA.
If you are still running into problems, please reach out to our Customer Success team at support @ aha.io.