Linking Issues in Comments looks odd

[Deleted user]

Hey there,

we use Jira on premise and experience an odd behavior in comments and descriptions of issues, regarding the link to other issues. An example would make it more clear:

When we reference another issue in an comment or description of a new issue, we simply put the Issue Key (as normally one will do) into the text, but the output (after saving or even on preview of the visual text) will look like this:

This comment wants to reference to the "PRO-27" issue, the "null"-Strings have not been inserted by the person, who created the comment, as seen in the following picture:

As far as i asked my admin of the jira software, he didnt change anything, which my be the cause of this problem. Is there anyone, who already had the same problems and / or knows how to resolve it?

[Thomas Deiler]

Dear @[deleted] ,

I recommend to open a support request at Atlassian.

So long

Thomas

[Deleted user]

Hi Thomas,

thanks for the Info, i just looked for an JIRA instance to open an support request with our SEN. But it seems that my company only got the starter licensen, so i am still in need to ask the community.

Dominik

[Thomas Deiler]

Dear @[deleted] ,

that's a pitty. But I doubt to be able to help you. Atlassian would ask you to send the support ZIP. Even if you do I am not from Atlassian nor I have a deeper knowledge of Jira (on source code level).

But anyhow, we can try.

1. Can you reproduce your issue at any time?
2. Is only PRO-27 affected?
3. Have you tried to create a similar comment with the REST API?
4. Do the log files show exceptions?
5. Have you selected special character encoding?
6. Are there browser add-ons active, that process content before submitting?

So long

Thomas

[Deleted user]

Hi Thomas, thanks for asking! I will respond to them using the numers as you did:

1. Yep, all other members and me can reproduce this issue at any time!
2. No, all issues and projects (old and even newly created ones) are affected without an exceptioN!
3. Yep, just created an comment via REST API, same result while displaying the issue (though the JSON-response doenst show this problem in the comment-string, seems just to be an displaying issue).
4. The log doesnt contain any exceptions or warnings reguarding this.
5. Special character encoding is enabled to UTF-8.
6. No browser add ons beside a small rest client, also it is not only my laptop, all pcs / laptops in the whole office are affected by this problem.

Regards,

Dominik

[Thomas Deiler]

Dear @[deleted] ,

ok - sound like a bug. If you provide me further Information like product versions, DB vendor, driver. I can try to raise a request in behalf of you. No guarantee.

So long

Thomas

[Deleted user]

Hi @Thomas Deiler  , thanks for this:

We use Jira 8.2.3 (exact name: v8.2.3#802003-sha1:5986657) from Docker Image (teamatldocker, which might be served as teamatldocker/jira > latest atm) using Postgresql as Docker image aswell (blacklabelops/postgres, might also be the latest image then).

Connection between Jira and PostgreSQL is set up via Docker bridged network, only Port 8080 is exposed to the host.

I already tried to set up the same structure on a new debian system, since we use docker-compose.yml-file for this): the problem did not occure on my freshly installed system here.

Regards,
Dominik

[Thomas Deiler]

Dear @[deleted] ,

this sound like an issue with the DB. Have you tried to cross link them? Just switch the DB between both instances and see if the error switches, too.

So long

Thomas

[Deleted user]

Hi @Thomas Deiler ,

i exported all of our projects to an XML file and imported them on a fresh and new DB with an fresh JIRA installation. The problem was solved this way, so we might change our production system this way aswell. No issue on atlassians JIRA needed anymore!

Thanks for all,
Dominik

[Thomas Deiler]

You are welcome!