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
  • Attach files
  • Tony Cleveland commented
    25 Jan 18:37

    I have seen this same behavior. In my case, I also had related master features assigned to a specific release. A more reasonable default behavior would be to put the imported feature with the master feature (if it exists) or just put everything in the parking lot. 

  • Jean-Francois Larente commented
    13 Feb 11:46

    Agreed with parking lot.

  • Rakesh Saharan commented
    02 Jun 16:24

    I agree

  • Trent Foreman commented
    03 Jun 15:46

    I would agree that this makes sense when integrated into a development software.  Having a default of where to put a new feature will help lessen confusion about where it lands.