Jira Product Discovery as an initiatives board

In my day-to-day activities, I utilize Jira Product Discovery in 2 ways: as a backlog of prioritized and unprioritized ideas, as well as a way to communicate the ideas/initiatives that are in motion. The first use case covers the process of generating ideas and documenting them for future discovery. The second use case is extremely useful when communicating with stakeholders across the org about the things in motion and their progress. The great integration between Jira Product Discovery, Jira and Confluence allows me to link the corresponding product requirements, UX flow and work items (epics, stories, tasks). Thus, the entire org is available to track progress, check details and stay on the same page. Jira Product Discovery allows you to use the predefined fields and benefit from tools like the effort/impact matrix, but it also gives you the flexibility to define custom fields and go beyond the one-size-fits-all solution. There are some limitations, though, e.g. timeline view of initiatives allows you to place a single entry per idea, which is not sufficient if you develop cross-platform solutions which may run at different paces. I believe this limitation is mainly there, as Atlassian offers dedicated tools for project management that are coming in the Premium tiers or as stand-alone solutions.