There is an approval process before a feature/release is record linked (set as a dependency) to another feature/release

This is useful for us since on how we use AHA, its our technical guys who does the linking of dependencies in terms of other features/releases to another. There are internal processes in terms of approval before a certain dependency (record link) is final already to be defined on a certain feature/release. If this is done, the tool can actually catch the manual process we will be doing before placing/defining the dependency (record link) per feature/release.

ADMIN RESPONSE

Sep 4, 2024

Thank you for the idea. Given the low volume of support for this idea, we do not have plans to make updates in this area at this time.

Attach files

Enter a subject

Idea management by

Create your own ideas portal to crowdsource feedback

Share your product feedback

Please enter your email address

RELATED IDEAS

There is an approval process before a feature/release is record linked (set as a dependency) to another feature/release