When sending a Feature to JIRA, automatically move the new JIRA epic/story into the JIRA project's Backlog

When we sync Aha! Features into JIRA, we're ready to begin planning sprints that will include the resulting JIRA epics/stories. Extend the JIRA integration so when new epics/stories are created from Aha!, automatically move them into the JIRA project's Backlog so they can then be added to a sprint during sprint planning.

This makes using Aha!-created epics/stories in JIRA a single-step action (i.e. Move epic/story from Backlog into sprint) instead of a two-step action (i.e. Move epic/story from JIRA project issue queue into Backlog, move epic/story from Backlog into sprint).

  • Gary Wu
  • Oct 31 2014
  • Already exists
Release time frame
  • Apr 6, 2016

    Admin Response

    This is the current behavior for the integration with Aha! and JIRA. When sending a feature to JIRA, it is automatically moved to the Backlog and can also include the specified Fix version.

  • Attach files
  • Niveditha Jayaram commented
    11 Sep 23:42

    When we move "Release" to "Sprint" in JIRA.  All the features go and sit in backlog. 

    Is it possible to move to automatically to the sprint we want to ? If so, how can it be done ?

     

    I followed the below "https://support.aha.io/hc/en-us/articles/360016062011-Sync-sprints-between-Aha-and-Jira-integrations-2-0-

     

    Here it clearly says that we need to give same sprint name what is present in JIRA. So, that all the features are moved to the sprint . Or else if the sprint with same name does not exists it creates one . Which is quiet confusing  for me .

     

    Can any one help?