Updating a feature does not cause requirements to update their release in integrations

Limitation with integrations 2.0 Jira.

With features mapped to user stories, requirements mapped to subtasks and releases correctly mapped to fix versions

Create Feature A, with Requirement A in Release A. Move Feature A to Release B.

Requirement A does not get it's fix version changed in Jira. Expected outcome is that the Requirement fix version would change to Release B.

  • Tom Bailey
  • Feb 7 2018
  • Shipped
  • Attach files
  • John Paul Grippa commented
    February 7, 2018 15:55

    This is not a feature request.  This is a bug!!!

  • Matt Wagnon commented
    February 7, 2018 20:36

    It worked this way with JIRA 1.0.  Do not "upgrade" if you haven't already.

  • Admin
    Austin Merritt commented
    February 8, 2018 03:35

    Hi everyone, we plan to implement a permanent solution for this soon. In the meantime, there is a workaround to get the requirements to update. After a feature has been moved to a new release, clicking the Resend all fields option next to the integration link will also resend fields for any requirements on the feature. This in turn will update the related fix version in Jira.

  • Matt Wagnon commented
    February 8, 2018 13:24

    Thank You Austin.  The upgrade to JIRA 2.0 haas been less than pleasant for us and nobody from Aha! has been able to get our Integration working since it was released.