Shipping a release should ship the features attached

When creating a release, features are "attached" to the release.  When the work is complete, shipping the release should automatically update the features to a status of Shipped instead of requiring someone to update each feature and the release.

  • Melina Barreca
  • May 31 2016
  • Unlikely to implement
Release time frame
  • Jun 3, 2016

    Admin Response

    Thank you for the request. It is an intentional design that we do not automatically set  feature statuses to Shipped when shipping a release as this can potentially cause inaccurate information when many features might not have actually been shipped. As you may have noticed, we intentionally move any non-shipped features to the following release.

    You should note that we do have some automation in that features which are marked as "will not implement" do not get moved to the following release because a resolution has been set for that item.

  • Attach files
  • Rachel Clements commented
    May 30, 2017 14:33

    Features become ready to ship at different times.

    I don't have an problem with updating each individual feature to 'ready to ship'.

    However, when I ship a release, I don't think it is unnatural to expect all features that are 'ready to ship ' will be automatically moved to 'shipped'.

    I understand that some features in a release may not ship with the release - but they won't be in a 'ready to ship' state, will they? So automatically move the 'ready to hip' features to 'shipped' when their release is shipped, and raise the outstanding issues in the release (that aren't marked as 'ready to ship')  for the user to resolve.

    That makes more sense that the user spending half a day painfully dozens of individual features to 'shipped' just so they can ship the release and not mess their reports up.