Add a new idea Subscribe
Status Future consideration
Categories Features
Created by Guest
Created on Dec 11, 2018

RELATED IDEAS

Choose Integration When Creating Feature

Very often PMs forget to send tickets to JIRA, when 95% of the time, they need to be sent. It would be great if on the create screen, one of the fields was the 'Send To' field so people can choose the correct integration upon creation & it's automatically set as they get started. 

  • Attach files
  • Martin Halliday
    Reply
    |     Oct 24, 2019

    I want to sync Aha Features to Jira Epics and Aha Requirements to Jira Stories.

    Assuming that I have already synced a Feature to an Epic, adding a new Requirement to the Feature automatically creates a Story in Jira. This is useful most of the time, but I have two different story types in Jira and Aha always creates the default one. This is OK unless I wanted the other story type, and in this case the workflow looks like this:

    1. Select a feature in Aha that is synced to Jira and create a new Requirement.
    2.  Aha creates a new Story in Jira of the default type (in my case this is called "Aha Product Story".
    3. I want this one to be a "Aha Tech Story" in Jira (not "Aha Product Story").
    4. I can't change the issue type in Aha, so I have to go into Jira and change the issue type to "Aha Tech Story".
    5. Aha tries to import the change but it fails with an error message saying that it doesn't match the integration.
    6. In Aha I have to find the Requirement and delete the integration link.
    7. Now I can re-link the Aha Requirement to the existing Jira issue choosing the "Aha Tech Story" integration.

    This is quite a painful process to go through for every new Requirement that needs to be mapped to the "Aha Tech Story" issue type in Jira.

    Having the ability to choose which integration to use on the create feature and create requirement screens would fix this problem very nicely.