Short links are only short sometimes

[Micheal Planck]

My link appears like this on a Confluence page: (note Risks | Cost reduction).

My link appears like this in the Jira description field: (note Risks | Cost reduction).

My link appears like this in the description field of a Jira Issue/Filter table on a Confluence page: (note https://mycompanygroup.atlassian.net/wiki/spaces/KEY/pages/2105737217/Risks#Cost-reduction).

Why? For the love of God, Montresor! WHY?

It would seem obvious that you would write a short link description routine, and then use that code everywhere you display a link. However, you have clearly written the code to display a link in every single instance where a link might be displayed, and you just missed this one because it was a layer deeper.

You will never fix this. In a decade this comment will remain, unaddressed, untouched, unnoticed; lost forever to the mysteries of time, just like Fortunato.

[Nic Brough -Adaptavist-]

Eh?  Could you explain the problem a bit more?  None of my users have a problem with any of the links they get sent.

[Micheal Planck]

Put a link in a Jira issue description field. It comes out short, like above.

Put the same link on a Confluence page. Again, short.

Then include the Jira issue in a Jira Issue/Filter table on a Confluence page. Make it display the description field in the table. The link comes out long, like above.

That is the problem: it works most of the time. But the Jira Issue/Filter table clearly uses its own code to display fields, rather than the code that Jira uses to display fields; otherwise, the fields would look the same regardless of which context they were invoked in.

Not only is this a bug; it is evidence of bad programming.

[Nic Brough -Adaptavist-]

This all works the same way for my users, so I'm a bit stuck on what you are seeing.

[Micheal Planck]

This code:

"As per" /link

/jira (single issue view)

/jira (table view)

Produces this:

If I do /jira (single issue), the link is invisible in the pop-up, but if I select "Full Screen" view then the link is properly displayed as short.

Are you saying you can do a /jira table view and links in your description fields are correctly displayed in Confluence Cloud? Why would we have different results?

[Nic Brough -Adaptavist-]

That sounds like you have a problem with your browser, as it's working fine for me and the people I work with.  Your screenshot is not showing a problem there either!

[Micheal Planck]

I don't understand your comment. The screenshot shows the problem. Do you not see the problem in the screenshot?

The first two links are as expected. The third link, in the table, under description, is not as expected.

EDIT: I am using Chrome as a browser.

[Nic Brough -Adaptavist-]

No, I don't see a problem in screenshots.  The description from the issue is being rendered as it is supposed to be - it's been extracted from Jira, it's not a macro that you've put links into so it can be rendered differently.

[Micheal Planck]

In Jira, when you view the description field, the link is displayed as a short link,

In Confluence, when you view the link, it is displayed as a short link.

In Confluence, when you view the link in a Jira Issue Table with the Description field, it is not a short link, The Jira Issue table in Confluence does not render the Description field the same as it does in Jira. This is the issue. The reason is probably because the rendering code is different. This is what I said in my very first post.

You do not appear to understand my comments, my issue, or what a short link is, even when presented with a picture; but you still felt comfortable gaslighting me about there being a problem at all and blaming my browser.

I can see why you are a Community Leader: you fit right in with Atlassian customer service.

[Nic Brough -Adaptavist-]

Yes, you are right, it's not your browser, I had to assume it was because of the information you had shared.  I am completely wrong about that.

It is this way because the tables don't understand that when they extract data from Jira, there may be stuff that you want to format differently, because you have not wrapped the incoming data in a link-rendering macro.

[Micheal Planck]

My apologies for my harsh comments. But Atlassian's approach to writing software is so alien to human experience that I sometimes forget there are (allegedly) human beings on the other end.

At this point, if we found out Atlassian was staffed entirely by ChatGPT, would anyone be surprised?