-
Bug
-
Resolution: Answered
-
Low
-
None
-
3.5.0, 4.2.0
-
None
-
Severity 3 - Minor
-
4
-
HTR:
- Create a commit with a dash right before the issue key 'test fisheye - ISSUE-1'
- Create a commit without a dash right before the issue key 'test fisheye ISSUE-1'
- Open the development panel on a linked JIRA instance
Expected:
- Both commits should be visible
Actual:
- Only the commit without the dash before the issue key is visible
Note: space character (' ') padding does not matter. This commit message will also fail: 'test-fisheye-ISSUE-1'
- causes
-
JSWSERVER-14890 Fisheye commit with issue key and - (dash) won't show up on the development panel
- Gathering Impact
- is caused by
-
FE-5254 Jira issue keys wrongly matched to review keys
- Closed
- is incorporated by
-
FE-6687 Jira issue development panel shows wrong commits
- Long Term Backlog
- is related to
-
CRUC-7067 Commit not recognized in JIRA when issue key is followed by colon
- Closed
- relates to
-
FE-4038 Reviews/Changesets/Issues which are not linked to issue are shown in Source/Review tab
- Closed
-
CRUC-7255 Commit messages with an issue key preceded by a dash are not visible in JIRA development panel, despite having perforce job set
- Closed
- clones
-
FUSE-2490 Loading...
- mentioned in
-
Page Loading...