https://getsupport.atlassian.com/browse/PCS-263435

this is a SERIOUS issue - there shouldn't be a way for users to bypass approval steps by moving an issue

This issue allows users to bypass the entire approval workflow. They create the issue in a project where they have the rights required to put an issue "in progress", and then move it to a project where they do not have the rights to approve issues.

Nicely hacked past the enforced workflow.

Because of this, as a product manager, I get confronted with pull request for features I did not know somebody was working on and where I don't even agree to the initial issue.

This leads to frustrations for all parties involved.

It would have been much better if this was stopped before it was even started.

This issue is now 6,633 days old.

This is a big issue as it provides a loophole for any sort of approval workflow when migrating issue types. Please implement a feature to limit the status options during migration.

At the moment, a user who is migrating a ticket from a different project can arbitrarily choose to put their ticket into whatever status they like. Our workflow (in the destination project) typically involves creating a submission review state before a ticket is accepted for work. It would be ideal if tickets migrated into our project could, by default, have their status reset to the creation status. This could be a checkbox.

Could we please expedite this bug.
I am not sure how this is considered as a feature request. This is a very common scenario to move issues from one project to another or one request type to another but once the issue is moved then it should follow all the steps of the new WF including the approval step. 

Let me know if we need to get into a call to get this ticket the right attention.

Thanks in advance for your anticipations!

This is a much-needed improvement required in Jira Service Management. Below is what we are facing on a day to day basis.

 
Project A with "Report An incident" Request Type and the workflow has these statuses- Open, In Progress, Waiting for Customer, Customer Responded, Pending, Resolved, Closed.
 
Project B with "Enablement Request" Request Type and the workflow has these statuses- Waiting for Approval, In Progress, Declined, Customer Responded, Waiting for Customer, Resolved, Closed.
 
Note that the "Enablement Request" ticket in Project B has to go through an approval process before it gets to the "In Progress" state.
 
Now, if I move an "In Progress" ticket of the "Report an incident" type from Project A to the "Enablement Request" type in Project B, as per your explanation, it will automatically skip the "Map Status" section in the Move screen. In this case, the ticket will be landed in Project B with In progress status. 
 
As I said any "Enablement Request" has to go through an approval process, but in this scenario, the approval process got skipped. And it creates a whole lot of confusion and process issues.

Well, ain't this a remarkable example of poor product management
Can't schedule a feature for 14 years? GJ Atlassian  

Repeating Dale Peters' question above, given this issue is open for 14 years, does anyone know an alternative solution to the problem? I.e. Is there a way (through an add-on etc.) to force all moved issues to end up in a particular status (e.g. Status: INBOX)?