Ability to add custom fields to the Release Phase view

In the context of a Launch Plan, Release phases can be used as work items, that together, make up the entire project plan, to come to a successful release. Examples of custom fields: a Release Phase can be assigned to a department and to an individual in that department. A Release Phase could be mandatory or optional and subsequently get a ‘tick in the box’ to indicate the status of completeness.

  • Guest
  • Nov 1 2016
  • Future consideration
Release time frame
  • Attach files
  • Nitin Aggarwal commented
    November 16, 2016 03:47

    This actually helps us to keep track of the of all releases at a glance and any specific Phase of release not as per planned can be made visible.

     

    Few Additions could be provide at Phase level a % Completion and Status Field (RED, Yellow or Green) and status field can help to spot which Phase is in danger of slipping out of being in red

  • Guest commented
    December 28, 2016 19:43

     I agree with the original request as well as Nitin's comments. Either custom fields or adding the fields Nitin suggested would enable us to track our launch criteria (or checklist) within Aha.

  • Guest commented
    January 11, 2018 22:13

    Two requirements:

    1) Assigning release phase to a person

    2) Method to have a status to track the release phase. This can also be achieved by allowing user to insert a custom field into the release phase.

  • Adam Kendall commented
    January 22, 2018 12:54

    I fully support this feature and the recommendations of the commenters. Having the ability to define a responsible individual for the phase would be massively useful. Right now we have the ability to see individuals responsible for features which in our use case is the designated developer and thus only relates to the 'Development' phase. But it would also be really useful to define for other phases such as 'Scoping', for example.

  • Matt Howard commented
    June 29, 2018 21:06

    We also have specific customers that will be receiving a version of our product release (beta or full), so we track these as release phases. If we could add a custom field to the release phase (customer), then we can build reports for our organization to view which of our customers will be receiving specific releases.

    As this idea shows as "Likely to implement" but was created two years ago - any idea if this will be implemented soon?

  • Guest commented
    July 13, 2018 14:47

    I would be interested in adding custom fields, to accumulate total value of a phase/release from the value of master features/features for a phase and ultimately release.  Kind of like we need a score card and workflow for phases......

  • Sam Richards commented
    October 10, 2018 18:27

    Being able to assign release phases to individuals would be very useful.

  • Mark Nixon commented
    16 Jan 19:22

    We use certain phases as checkpoints and would prefer to indicate in dedicated fields of each stakeholder's vote such as Go/No Go, Met/Not Met and Comments. Since there multiple stakeholders this would be best facilitated in a table.

  • Guest commented
    21 Mar 14:21

    Would love to see this added soon, as it would be used to resolve some concerns around sprints/iterations vs. actual releases/launches. 

  • Phil McNair commented
    25 Mar 15:28

    having the ability to add custom fields to release phases would be really helpful for what we're trying to visualize. Currently, our projects are releases and the shared resources are listed as phases. We also want to show the level of effort for each phase, so having the option to either (1) color-code or (2) show on a pivot would be very helpful.