The commit message that you submit should put the subtask in the permission state, assuming that it is in a state with Resolve permission available and that you do not need the subtask to determine the resolution when it is resolved.
If this does not work, I see several possible reasons:
- The subtask is in a state without an allow transition.
- The subtask does not have permission by default and requires that one be specified with permission
- Subtask has one or more required fields not defined by SmartCommit
- A subtask requires rights that your SmartCommit user does not have to solve.
- There is an error in [Fisheye]: https://answers.atlassian.com/questions/96530/can-i-resolve-an-issue-s-sub-task-using-a-fisheye- smart-commit] on the Atlassian forum Answers
A quick comment on something else that you said in your question in passing:
FishEye will solve the parent problem (and presumably the subtask when it was on it).
This is not the default behavior for JIRA workflows. If you want subtasks to be resolved with parent permission, you will have to set up the workflow.
When resolving a parental decision, when all his children are allowed in behaviors that, it seems to me, are appropriate in some cases, I am not at all sure that resolving subtasks when a parental decision is allowed is not suitable at all.