I have a similar question to the previous related to Fix Version 4.1.2, which doesn't appear in the official list of latest available hotfix versions. Is there any additional information on when this release will occur?

Fix Version/s: ..., 3.16.4, ...

Where to download SD v. 3.16.4 obr ? Anyone?

As far as I can see, the latest available version is 3.16.3
https://marketplace.atlassian.com/apps/1213632/jira-service-desk/version-history 

Hi Drew, 

As a said, it is "For those that are affected by this bug, but not having 50 comments on the issue".

It was mi case, and I wanted to help sharing the solution I found.

To check if it is your case, just create a new comment linking the same file without any alias, and check if the previous alias link is working properly.

Regards.

Manuel thanks for the workaround you provided for the other pipe 403 error Atlassian had,  JSDSERVER-6082,  but I don't see this workaround providing any solution for this issue. The reason is simply once you get over 50 public facing comments the comment with an attachment, regardless of it being with an alias or not, will give a 403 error. Your Script when it creates another comment will still be a comment higher than 50, it doesn't add the attachment to a previous customer facing comment nor change an earlier customer facing comment to internal which are the workarounds that do work. If I am wrong or misunderstanding your comment my apologies.

Hi,

For those that are affected by this bug, but not having 50 comments on the issue, I want to share the workaround I have develop for this bug JSDSERVER-6082.

I discovered that if the linked file is also linked in another comment without alias, the links with alias works.

With that info, I have created a Script Runner Listener on comment creation and comment edition of Service Desk projects.

If a public comment is created or edited, and that comment contains file links with alias, the script cretes a new comment only with the linked files, but this time without alias:

import com.atlassian.jira.bc.issue.comment.property.CommentPropertyService
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.event.issue.IssueEvent
import com.atlassian.jira.issue.comments.Comment
import groovy.json.JsonSlurper
import java.util.regex.*

final SD_PUBLIC_COMMENT = "sd.public.comment"

def event = event as IssueEvent
def user = event.getUser()
def comment = event.getComment()
def commentPropertyService = ComponentAccessor.getComponent(CommentPropertyService)

def isInternal = { Comment c ->
  def commentProperty = commentPropertyService.getProperty(user, c.id, SD_PUBLIC_COMMENT)
  .getEntityProperty().getOrNull()

  if (commentProperty) {
    def props = new JsonSlurper().parseText(commentProperty.getValue())
    props['internal'].toBoolean()
  } else {
    null
  }
}

if (comment && !isInternal(comment)) {
  String txt = comment.getBody()

  def files = []
  Pattern filepat = Pattern.compile("\\[.*\\|\\^(.*)\\]")
  Matcher m = filepat.matcher(txt)
  while (m.find()) {
    files << "[^"+m.group(1)+"]"
  }

  if(files){
    def commentManager = ComponentAccessor.getCommentManager()
    commentManager.create(issue, comment.getAuthor(), files.join("\n"), false)
  }
}

This way, the original alias link works ok.

I hope this may help.

Regards.

Hello, I agree with Eric, and this bug is causing significant disruptions to our operations.

This has affected a critical reporting project in our organization. Please resolve. Thanks.

Like David, we are also really suffering from this issue. Most of our communications with external customers involve more than 50 public comments and the attachments contain essential information regarding the request. Please prioritize!

>Priority:  Low

That's all I needed to know before even considering moving to service desk.

We really suffer from this error now. We cannot follow up CR's with our customers since attachments won't show. 

A ticket system that cannot handle 50 comments on an issue..? I know if was April 1st yesterday, but still remains April 2nd..