Default post functions order causing values added in transition to be denied with certain status' property

Summary
Default post functions order causing comment added in transition screen to be denied with certain status' property:

• jira.permission.comment.user set to denied/false

Cause
This particular check is only meant to apply on transitions when the source state and target state restrict adding work to an issue. Permission checks for comments were only looking at the target state causing comments to be ignored. 

Steps to Replicate

1. Add a workflow property at the destination step: jira.permission.comment.user value denied
2. Add a screen to the transition to the destination step above, which have the field included
3. Publish the workflow
4. Try running transition with a value in the restricted field from destination step.

Expected Behavior
Comments can be added during the transition if the user has permission to add comments in the current state, or in the target state for the transition. 

Actual Behavior
The workflow property is in place and causing the transition the value to be ignored.