Details
-
Bug
-
Resolution: Duplicate
-
Low
Description
JIRA OnDemand - Text Display - Integers immediately preceded by the letter 'r' display as null strings
Steps to Reproduce
- Create an issue
- Enter the following text into the Description field: "r12345"
- Submit the issue
- Enter the following text into the Comments field: "r12345"
Expected Result:
User-defined text displays as entered, with any Wiki Markup formatting applied
Actual Result:
The string does not display at all (null string) for either the Description or the Comments field
Impact:
- Developers are used to entering references to changes they make by referring to a specific commit revision
- They are in the habit of writing this in the format: "r#####" (e.g. "r12345")
- If they maintain this habit, JIRA currently does not display this crucial information
Notes:
- If you go back to edit the field, the text is still there
- This appears to be a relatively new issue, I've only noticed it happening within the past week or so (current date is 27-JAN-2014); I feel like I probably would have noticed this behaviour sooner if it had been happening for a longer time
- I have taken a look in the JIRA Admin panel and can't see anything obvious that could be causing revision references in this format to fail to display
- The project affected can be found at warchest.atlassian.com
- We have many non-default add-ons installed (FishEye, Cruciple), but we don't actively use any of them as far as I can see
Attachments
Issue Links
- duplicates
-
JRACLOUD-66239 Fisheye changesets and revision numbers are not being rendered JIRA comments when JIRA OnDemand is not linked with Fisheye Standalone.
- Closed