We are using the Jira Spoke Create Issue action to create issues in our on Prem Jira application. It requires the selection of a project and issue type, which get stored as project id and issue type id (numeric values) and sent to Jira. We are moving to Jira cloud and have found that all of our flows are broken using the Create Issue action because the project id and issues type id values stored on the action do not exist in migrated Jira cloud data. When we expand the action in each flow it fails to populate values, which is leading us to have to reselect each value for the action; we have 100+ flows.
Per our Jira admins, project ID cannot be maintained when moving to cloud, and moving forward, we should build integration utilizing project key which will remain constant. Our version of the Jira Spoke does not allow us to use anything by project and issue type id. There are other Create Issue calls that utilize project key, but they are all deprecated.
Anyone run into this issue and have suggestions on a way forward?
Thank you
