Issue: built many flows using the Jira Spoke Create Issue action. The action presents lists of projects and issue types that are pulled from Jira. The underlying values (IDs) are then stored in the flow. When we move these flows from lower env. and put them to a different Jira env., if the underlying ID values are different in the new env. the flows break. With on-prem Jira this can happen. It is also happening when we move to cloud. The project IDs and Issue type IDs are going to be different which means all of our flows will break. The only solution is to manually rebuild each while pointing to the new cloud env.
Would like to find a way to avoid embedding IDs in flows so we avoid the issue in the future.
Has anyone run into this and care share their solutions?
Thank you
