-
Suggestion
-
Resolution: Unresolved
-
None
-
55
-
Issue keys are scanned via a regular expression, and not validated against the Jira server. This can result in false-positive Jira issues, such as UTF-8 or ISO-9001. Users cannot know whether or not they made a mistake when they typed the issue key unless they check the Jira issue they meant to reference.
- is cloned from
-
BSERV-2470 JIRA Integration: Check for issue validity before linking issues
- Closed
- is duplicated by
-
BSERV-3050 Stash parse UTF-8, RFC-3659, SHA-256 etc as JIRA keys
- Closed
-
BSERV-2528 only link commits to tasks, if the project is linked
- Closed
-
BSERV-4874 Ability to add plugin for Issue Tracker integration
- Closed
-
BSERV-7282 Escape charater to prevent JIRA issue pattern
- Closed
-
BSERV-11709 Do not create Jira key links in comments if key does not exist
- Closed
- is related to
-
BSERV-4924 Jira issue parsing in Stash commit
- Closed
-
BSERV-3090 Automatically link JIRA keys in PR description and comments
- Closed
-
BSERV-3099 Support custom linkers
- Closed
-
BSERV-11716 Ability to display only new Jira issue number in pull request when user changed project KEY in Jira
- Gathering Interest
- relates to
-
BSERV-5273 Commits with the string "UTF-8" or "UTF-16" create a link to a non-existant Jira bug
- Closed
-
BSERV-10341 JIRA smart links and commitid overwritten with links even it's a part of another markdown object
- Gathering Impact
-
BSERV-10561 Provide single admin interface for the integration regex customization
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Wiki Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...