-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 7.2.0, 7.6.9, 7.12.3
-
Component/s: Issue - Comments
-
7.02
-
6
-
Severity 3 - Minor
-
1
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
I followed a link to an issue which had a trailing comma after the issue key in the URL. It displayed with no indication that there was a problem. On trying to add a comment, I got the Communications Breakdown error ("The JIRA server could not be contacted.").
- An example of how this can occur is ending a sentence in a Google Doc or email with the Jira URL. The link could include the end of sentence punctuation.
While this is clearly an edge case, it happened on a link that was detected in text, with the following comma being included in the URL.
Steps to Reproduce:
1. Open a issue and add "," (comma) to the end of the url. This could happen when user click on a link in a chatroom.
2. Add a comment to the issue.
Expected Result:
Some earlier indication that there's a problem, or for all operations to work. An upfront 404, redirection to the correct URL or for commenting to work.
- In versions prior to 7.2.0 the issue would not load. "Issue does not exist" or "This issue can't be viewed"
Actual Result:
Got the Communications Breakdown error ("The JIRA server could not be contacted.").
- is duplicated by
-
JRASERVER-68782 Adding any string at the end of a plain issue URL causes communication breakdown when commenting
-
- Closed
-
- relates to
-
JRACLOUD-63686 Unable to comment on issue when URL includes extraneous comma
-
- Closed
-