Hi Earl,
Thank you for answering my question, I get it.
My feedback to the Atlassian team here is while in the ideal world data from JIRA flow back to Portfolio and update the scope items/GANNTs in there, the reality is that very rarely the data in JIRA (boards, projects, etc) is kept (enough) up to date or clean enough at a hygiene level. That said, there's definitely value in a Portfolio-to-JIRA commit upon initial scope item (epics, user stories, etc) creation as it eliminates duplicate data entry.
In regards to my own (very selfish) use cases - I just want to take advantage of Portfolio's amazing ability to let me do top-down planning with what-if analysis...I don't want to commit data to JIRA as there's no one to run with those scope items (yet or at all). The scope focus may not even be agile development, but more operations focused (e.g. music content/metadata/rights prepping and packaging).
I want the ability to quickly answer such questions from the executive stakeholders as "What if we had a special agreement with an XYZ company and wanted to deliver 5,000 songs (ie, audio files/metadata, etc) for the Independence Day events, can you deliver?; What's the impact to the timeline if you keep resources the same? How many resources would you need in addition to the current capacity in order to hit that date?"
Thank you,