If we want to have one initiative assigned to one piece of work/feature, we have to create a custom initiative field. However, when adding this custom initiative field, we can no longer associate it to the rest of the initiative information.
For example, we pull a report and try to show the initiative description with that initiative title (from the customized field) and associated work/features. But any info from that initiative form does not show up. Even though we are selecting from the same list of initiatives, the data is not connecting when we try to pull it into reports.
Ok, thank you so much for the additional information. That is very helpful.
I am going to mark this Future consideration so we can continue to monitor customer feedback in this area. Thanks!
Hi Austin,
That would be awesome if we could pull multiple initiatives in the regular initiative field within a feature. However, since we can't, we used the custom initiative field to allow us to add multiple initiatives to one feature. But with this custom field belonging to the feature now, when we try to pull a report with those initiatives and features, it will be not pull the initiative description into the report. We tried to build the report both ways (feature first in hierarchy then initiative and vise versa) to see if either way would allow the initiative description to pull into the report but it doesn't. So the use case is to be able to pull record related information from the initiative into a report when using the Initiative custom field within another record type.
Hi there, thank you for your idea. Is the use case that you need to associate more than one initiative with a feature? Thanks!