

Seventy percent of these errors are perceptual in nature, i.e., the radiologist does not "see" the abnormality on the imaging exam, perhaps due to poor conspicuity, satisfaction of search, or simply the "inexplicable psycho-visual phenomena of human perception." The remainder are cognitive errors: the radiologist sees an abnormality but fails to render a correct diagnoses by attaching the wrong significance to what is seen, perhaps due to inadequate knowledge, or an alliterative or judgmental error. Retrospective studies disclosed then and still disclose today that diagnostic errors in radiologic interpretations of plain radiographic (as well as CT, MR, ultrasound, and radionuclide) images hover in the 30% range, not too dissimilar to the error rates in clinical medicine. In the more than half-century that followed, Garland's pioneering work has been affirmed and reaffirmed by numerous researchers. He focused their attention on the fact now known and accepted by all, but at that time not previously recognized and acknowledged only with great reluctance, that a substantial degree of observer error was prevalent in radiologic interpretation. Garland almost single-handedly shocked the entire medical and especially the radiologic community.

Since you cannot edit the filename of an attachment on an existing Jira case, this looks to be the only way to avoid this problem when it comes to Service Desk.During the 10-year period beginning in 1949 with publication of five articles in two radiology journals and UKs The Lancet, a California radiologist named L.H. I realize this is not an ideal solution, but I would recommend that if you need to attach more than one screenshot in the same issue of Jira, to instead save these as image files on your system first and give them uniquely different filenames before you upload them to Jira.

There is an existing documented bug on this problem in. But for Service Desk, customers can't see images unless these are referenced in the comments via the wiki markup syntax. In Jira Core/Software issues, users can still see all the attachments on the issue under the attachments section. This is not as much of a problem outside of Service Desk. I suspect that JSD Agents and Jira Core/Software users looking at this issue in the main Jira site will be able to see both attachments. The way to confirm this though would be to look at this issue through the Jira main site (not via the customer portal). I believe that it is not technically overwriting the first image.

The problem here is how is Jira supposed to understand which file with that name is supposed to be rendered here. Jira has to use a markup which tends to look something like this: The problem here is that when you then paste a different image with the same name, Jira does not have the proper means to differentiate between two files with the same name on the same issue when trying to display that image inside a comment. So when you paste an image into Jira, by default it uses a filename such as 'image.jpg'. I think the problem here is the way these images are being added, and the method in which this happens.
