Allow Feature or Master Feature to be pushed to Jira when the Aha! state is mapped but blocked when it is un-mapped

Our product management team wants to plan features prior to making the feature available via Jira Integration.  For example while a feature is under consideration or in planning/grooming state it would only exists in Aha.  Once the feature is ready for development it would be pushed to Jira.   The push to Jira should be automated

  • Guest
  • Dec 18 2019
  • Future consideration
Release time frame
  • Attach files