Steps to repro:
1) Create a Jira case
2) In the comments drag a file and submit
3) Create a different file with the same name and extension
4) Drag this file in a new comment and submit
Expected: The link in the second comment will open the file from step #4
Actual: Link in the second comment will open the file from step #2
More info: In the attached file area we will have the original file and the second file with some hash attached to it so they had unique names. For some reason in the second comment instead of having the link to the file with the hash, it points to the file without it
Usecase: I am adding an archive from the log directory which name doesn't change. There is often a lot of confusion from the devs about why the attached logs are from old builds when in fact the new logs are attached but linked incorrectly due to this Jira bug
It appears there are two open "suggestions" related to this symptom in the public backlog. You may watch/vote for them here. One is very old, indeed!
https://jira.atlassian.com/browse/JRACLOUD-2169
https://jira.atlassian.com/browse/JRACLOUD-67875
Best regards,
Bill
Hi @Bill Sheboy !
Mentioned issues are somewhat related but not exactly the same.
I have already been using my own workarounds, but anyway, the scenario is very common, I and everybody else intend to use it the same way and we will encounter this bug again and again until this is fixed.
Each time we forget about this issue, we lose around 2h of at least two engineers, so you can imagine we get quite angry about the bug which cannot be fixed for so many years.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information. If you believe this is a different defect, you may ask your site admin to submit a support ticket to Atlassian to investigate:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you serious?
After spending multiple minutes on finding a place where to report a bug and then spending my time on the report, this is the only response I get?
Forget about it...
P.S. In case you are not employed by Atlassian, no offense Bill. I don't see if you are representing them or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope, I am not an Atlassian employee; just a fellow user trying to help. When I have a defect to submit I also need to do that through my site admin.
As you have already recorded the symptom and repro steps, your site admin should be able to quickly create the defect and get a support person in touch with you.
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy
My apologies and thanks for the answer:)
Very strange, that actual users cannot report a bug directly to Atlassian. This definitely discourages me to do any bug reporting in the future.
Kaspars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.