Require completion of certain fields with promoted ideas
Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
At least we should have an entry in the red rectangle (see screenshot) saying "Promote to Feature (Pop-up) to update the Promote Idea popup.
The same as the other entry of the Custom Builder, we need to be able to tell if some fields are required or not. Basically, we like to give an initial estimate when we promote Ideas to Features. It would greatly help if we can do directly here in this popup.
We frequently promote ideas to features, but the two records don't share the same (required) fields. It'd be great to enforce the required fields upon promotion, so we can maintain our data hygiene.
This should not be treated as a new feature enhancement, but as a bug. This is causing inconsistencies on how we manage and track data across the portfolio.
* Make some feature properties mandatory. * When creating a feature manually: You will be asked to provide those mandatory feature fields (which is good) * When importing features from a csv spreadsheet: you will not be asked to provide those mandatory feature fields (which is OK IMO) * When promoting an idea to a feature: you will not be asked to provide those mandatory feature fields (which is NOT OK IMO).
If Aha! can pause the user (while promoting an idea) to ask him to assign a release, Aha! can also ask the user to provide the mandatory feature fields to enforce having them filled up
At least we should have an entry in the red rectangle (see screenshot) saying "Promote to Feature (Pop-up) to update the Promote Idea popup.
The same as the other entry of the Custom Builder, we need to be able to tell if some fields are required or not. Basically, we like to give an initial estimate when we promote Ideas to Features. It would greatly help if we can do directly here in this popup.
We frequently promote ideas to features, but the two records don't share the same (required) fields. It'd be great to enforce the required fields upon promotion, so we can maintain our data hygiene.
This should not be treated as a new feature enhancement, but as a bug. This is causing inconsistencies on how we manage and track data across the portfolio.
Scenario:
* Make some feature properties mandatory.
* When creating a feature manually: You will be asked to provide those mandatory feature fields (which is good)
* When importing features from a csv spreadsheet: you will not be asked to provide those mandatory feature fields (which is OK IMO)
* When promoting an idea to a feature: you will not be asked to provide those mandatory feature fields (which is NOT OK IMO).
If Aha! can pause the user (while promoting an idea) to ask him to assign a release, Aha! can also ask the user to provide the mandatory feature fields to enforce having them filled up