• Type: Bug
• Resolution: Timed out
• Priority: Low
• Fix Version/s: None
• Affects Version/s: 5.8.1
• Component/s: Encoding
• Labels:

  • bamboo-bugs-grooming
  • da-encoding
  • da-special-characters

[BAM-17780] UTF-32 character in XML can cause issues

Collapse comment: Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:10 PM

Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:10 PM

Atlassian Update - 23 June 2020

Hi,

Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

Thank you,

Bamboo Team

Expand comment: Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:10 PM

Martyna Wojtas (Inactive) added a comment - 23/Jun/2020 3:10 PM Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

Collapse comment: jim weaver added a comment - 25/Aug/2016 2:40 PM

jim weaver added a comment - 25/Aug/2016 2:40 PM

Just a note that if you hit this bug, you must locate and remove data from the database manually. Log files will point you to the build plan and table with the problematic character(s) - you must use a SQL client to clean it up. Until you do so, the bug causes two symptoms:

• The search boxes in bamboo will be unable to search against any build plans. You will be unable to reference from one build plan to another where a text search is used against build plan names.
• Bamboo will completely hang an a startup - so it is best to leave the instance running until you have removed the data.

Expand comment: jim weaver added a comment - 25/Aug/2016 2:40 PM

jim weaver added a comment - 25/Aug/2016 2:40 PM Just a note that if you hit this bug, you must locate and remove data from the database manually. Log files will point you to the build plan and table with the problematic character(s) - you must use a SQL client to clean it up. Until you do so, the bug causes two symptoms: The search boxes in bamboo will be unable to search against any build plans. You will be unable to reference from one build plan to another where a text search is used against build plan names. Bamboo will completely hang an a startup - so it is best to leave the instance running until you have removed the data.