Please can you please remove the ability to promote an idea to a master feature if:
1. Master features are not enabled on any product within an account, remove the ability to promote an idea to a master feature entirely.
2. A product does not have master features enabled, users should not be able to promote ideas to that specific product.
If all workspaces in your account have epics disabled, then the 'Promote to epic' option will not be shown. To find which workspace is using epics, you can create a report of workspace settings and include the column 'Epics enabled.'
I feel that this needs to be reviewed so that it does not apply at an account level. We have lots of non-product teams now using Aha! for their own use cases (project based) which is something promoted by Aha!. They don't have the concept of Epics but when promoting an idea they still get presented with options that are not applicable to them, which has already caused confusion. If there are different use cases for different teams to be able to utilise Aha! then there should be customisation at a level that is below the master account.
This feels like a bug to me- disabling a record should hide it from the entire account. Not ideal to need documentation to ensure users aren't creating a record they'll never be able to access.
Master Feature is disabled across all products in our Idea Portal but when a PM goes to to promote an Idea they are given the option to promote to Initiative, Master Feature, or Feature. This is VERY confusing because they don't know what a MF is and if something is accidentally promoted to that level, it's now unviewable. I was under the assumption if MF are disabled they are disabled everywhere.