...
Subdirectory - if you specify a path to a folder into this field then , any new story files will be added to this directory; if you leave this field blank then new story files will be added to the root folder of the repository. Note that this field supports the use of the following placeholder ‘${component}', e.g. ‘src/test/resources/${component}/stories', in this example if the issue to which the story is attached happens to have the issue component field populated e.g. ‘componentA’ then the added story will be placed into the directory “src/test/resources/componentA/stories“ and if the issue’s component field is blank then the directory path used will be 'src/test/resources/stories'. If the issue happens to have several values for the component field, then only the first one specified will be used and others ignored.
Committer name - value to use in for the committer name attribute of the git commit; if . If left blank then the name of the Jira user making the changes will be used. Note that Jira user name will always be used for the author name attribute of the git commit irrespective of this field.
Committer email - value to use in for the committer email attribute of the git commit; if . If left blank then the email configured in Jira belonging to the Jira user making the changes will be used. Note that Jira email address will always be used for the author email attribute of the git commit irrespective of this field.
...
Often while using Git teams would be following a Git feature branch workflow where changes are made on branches other than the base branch (e.g. feature, bugfix, etc.) and then merged into the base branch (e.g. master) after code reviews and other checks that teams may have setupestablished. To turn on support for Git feature branch workflow enable the option shown in the screenshot below.
...
If the Jira issue doesn’t have a story file attached yet and you add it via the plugin interface the git branch will be created automatically and the name used will be “refs/feature/<issue_key>“. You can of cause create the git branch manually yourself also e.g. by using a link under the Development panel on the view issue screen, but you must specify the issue key at the beginning of your branch name, e.g. if your issue key & title are something like “DEMO-123“ and “Implement feature A“ you may specify a branch name like “refs'refs/feature/DEMO-123_implement_feature_A“A'. The plugin will search for a feature branch starting with the issue key of the issue that you are viewing in order to check if the issue has a story attached or not.
...
Story file names must always start with the Jira issue key
When you add a story to an issue using the plugin interface the file that will be added to the repository will be called “<issue_key>.story“ e.g. DEMO-123.story. If you want to add a story file by other means (e.g. by a git command line client) then ensure that the name of the file also starts with the issue key, e.g. “DEMO-123_feature_A.story”. The file can be placed into any directory of the git repository, just so long as there is just one story file per Jira issue. If you add more than one, then the first file found will be shown by the Jira plugin and others ignored.Issue branches must always start with the Jira issue key
Applies only while using GIt branch workflow support. See explanation above under Git branch workflow support section.There must be only one branch per Jira issue
Applies only while using Git branch workflow support. If you happen to create more than one git branch for a Jira issue, then the first branch that starts starting with the issue key found will be used by the plugin.
...