...
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 starting with the issue key found will be used by the plugin.History does not follow renamed files
If you happen to rename the story file (e.g. via git command line client) for example from say ‘DEMO-123_implement_feature_A' to 'DEMO-123_implement_feature_B’ then although the issue key remained the same the renamed file would be treated as a new file from the story history perspective.