https://confluence.atlassian.com/display/STASH/Using+branches+in+Stash outlines the branching model we're adopting.

However, when you click "Create branch" from a Jira issue, the "Branch type" default value is based on the Jira issue type you just came from, not the branch you're branching from.

I would expect changing "Branch from" from "develop" to "master" would change the "Branch type" from "feature" to "hotfix". It even makes sense to disallow developers from changing this default. However, changing the source branch changes nothing. The "Branch type" default type is derived from the Jira issue you create the branch from. Currently, it's up to our devs to remember to select the right branch type.

"New Feature" defaults to a "Feature" branch.
"Story" defaults to a "Feature" branch.
"Bug" defaults to a "Bugfix" branch.
"Task" defaults to a "Bugfix" branch.
"Improvement" defaults to a "Bugfix" branch.
Custom issue types default to a "Bugfix" branch.

This makes misnaming branches that break your branching model too easy. If it defaulted to the right name, it'd help enforce the branching model.