Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong.  Today, the destination of imported items seems almost up to chance although there seems to be a pattern in going to the next upcoming release.  One has to go looking for the imported items immediately after import so as to file them away appropriately.  (When Integration 2.0 for TFS was released last week, imported items were going to the very first release ever, but someone seems to have changed that since then.)  I don't think it makes sense to define the destination in the integration definition because releases and parking lots are dynamic.  To that end, I tend to think that the user would need to define the destination each time they import so they can choose from the options available at the time.

  • Tom Beck
  • Mar 7 2018
  • Future consideration
Release time frame