Independent Release Phase Dates

Currently, Release Phase dates are 100% dependent on the Features within, however, we often need time after dev work is complete to finish the To-Do's (non-technical work) of the Phase itself - but you can't extend out the phase. 

It makes more sense to have the Phase timing be independent to account for the non-technical work that needs to be completed as well. 

  • Robyn Diamond
  • Jul 30 2018
  • Planning to implement
Release time frame
  • Aug 10, 2018

    Admin Response

    Thank you for your idea. We would recommend adding a second phase in the case where there is non-technical work to be tracked. When no features have been added to a phase, you are able to control the start and end dates manually.

    Based on the flexibility noted above and other feedback, we do not have plans to make changes here at this time. We hope you can understand.

  • Attach files
  • Robyn Diamond commented
    August 14, 2018 20:14

    Hello Idea Admin - Our release phases are static (Closed Beta, Open Beta, GA) so simply adding another random phase isn't an option. This level of standardization is needed as we have very cross-function projects to deliver.

    You also can't adjust Release Phases based on the To-Do's within in it. That's how we currently track Non-technical work (Features are technical) so if all related records- not just features - could impact Release Phase dates, I'd be open to that as well.

    Should I submit a separate Idea for that??