Hi Karol,

please take a look at this https://docs.stiltsoft.com/display/CATAT/Commenting+on+Attachments

If you get interested in our app, please drop an email to vrutkevich@stiltsoft.com.

When can we have this implemented?

This bug is not fixed at all. Why is it closed?

Oh look, this issue was closed without being properly resolved and now it is closed we can't add any more votes to it.

Replacement issues are still open, but of course they have far fewer votes.

Sure we could buy an add-on to do this, but it really should form a basic part of the jira comment mechanism.

I've just had to manually add in a link because a comment to one of my tickets made no sense. I also wasted ages trying to work out how to make a text file (actually a python script) display inline, but the documentation steadfastly refuses to explain how to do that.

Here is the incredibly useful comment I saw:

Blah. Blah.

The solution is to do this is

A completely unrelated comment

It was only when I noticed that there was an attachment added in the same comment e-mail that I realised that the solution was in the attached script.

Wouldn't it have been so much easier if the comment had been created as:

Blah. Blah.

The solution is to do this is [^filename.py]

A completely unrelated comment.

I think that everyone who voted on this issue should now vote on JRA-34927 and see if we can get something done about it.

@all

please vote on JRA-34927 in order to speed this up

Email Only; for what its worth, JEMH can auto generates comments with file download links and image thumbnail wiki markup as well as render images full size inline for emails containing attachments.

activity stream is not a viable substitute for the requested feature - attachments should have comments/description associated with them on the page.

Agreeing with Philip and Dieter - there needs to be an outlet for requests to improve this feature.

In our JIRA 5.0 installation, the default tab panel is Comments. I'm presented with confusing comments that were intended to be associated with attachments, but aren't; and attachments that were intended to have associated comments, but don't. Both are bewildering. Never in my wildest dreams would I guess that to find out which goes with which, I would click on "Activity". (Not "Activity Stream" anymore, contra what Bryan wrote.) Even once my coworker and I learned that it was under "Activity Stream", it took us a good while to find that tab on the issue page. The "All" tab also includes this information, if you know what to look for, but it's still far from clear that a given comment goes with a particular attachment.

We have non-IT customers who we are trying to help use JIRA, to facilitate the workflow of requesting features, prioritizing issues, and user testing and closing issues. They already resent being asked to learn another IT system, and difficult-to-use features like this discourage them from believing it's worthwhile.

I'm not saying this is necessarily easy to fix. I am saying that it's a major forehead-slapper for people who use JIRA. (Especially those who come here and realize the issue has been known for almost 9 years.) And there needs to be a new issue where people can request improvement.

(Update: I added JRA-27872 to track the part of this issue that hasn't been addressed. Since you can't vote for this one, feel free to vote for that one.
Then I found these other related issues:
JRA-1062: Attachment icon in comments
JRA-3594: Ability to add a description to an attachment (instead of a comment?)
JRA-21394: Automatically include attachment link in attachment comment)

I also agree with Philip... I think Atlassian should create a seaprate Issue where all users can vote, which are NOT satisfied with the solution "Activity Stream"...

Wow, definitely agree with Philip and everyone else. Very well explained Philip. It is clear that this is not fixed, so at least re-open it and say that you're not going to address this at present or something reasonable.

SHOCKING!! THIS IS CLEARLY NOT FIXED!!!

The simple request is, when adding a screenshot/image and simultaneously adding a comment, the comment when appearing in the Comment stream/tab should AUTOMATICALLY contain a thumbnail of the referenced screenshot/image! Just like this (image thumbnail followed by filename hyperlink):

gnome-about-logo.png

When clicking this thumbnail, the screenshot/image should either open in a lightbox, or navigate to the screenshot/image URL (as per current click functionality present on screenshot/images in the "Attachment" area).

Further, the screenshot/image should still be visible in the "Attachments" area of the issue, as per current functionality.

• Activity Stream is nice, but not the solution.
• Wiki markup is great as an "advanced" feature, but this is a basic intrinsic feature that novice users shouldn't even have to think twice about.

**Insanely shocking** that a ticket can be resolved/fixed when so many users are clearly stating that an adequate solution has not been reached! Which makes me wonder, what is the point of Atlassian having a public issue tracker at all??! Do your product justice and PLEASE re-open this!!

Can somebody from Atlassian please describe why this is marked as "Fixed". We run JIRA 4.4.3 and I can't see the requested feature.

Not fixed. Please re-open.

I do not understand why this issue is closed as I can't see the feature of comments side by side to the attachments implemented...

I've created JRA-21394 to deal with adding a link to the attachment in the attachment comment. I didn't want to simply jump in on this ticket since it headed in the wrong direction and I didn't want to further muddy the waters. Hopefully this gets fixed. It really shouldn't be that big of a deal, IMHO.

I agree with Dmitry and sebbapache; This was not really the solution we were waiting for. This feels more like a workaround than a real fix.

Would it be that hard to automatically add link(s) to the attachment(s) directly in the comment field? That way they would be visible directly in the comment tab.

The activity stream seems to be a nice way to look at the most resent activity. If you want to look at all comments and/or see the comments for added attachments, the comment tab feels like a better alternative however.

The activity stream is not exactly easy to follow, as it contains lots of extra detail.

And it's in reverse chronological order (perhaps to make it easier to drop the earlier sections).
And of course the earliest sections (which are likely to have important attachments) are not necessarily visible.

Seems to me that the original issue has not been addressed at all, let alone resolved, and should be re-opened.

Bugzilla does this much better

test. new file attached.
Not the solution i expected.

We have bundled the activity steam into JIRA 4 - so you can now see attachments in line with the issue comments.

This is seen by clicking the Activity Stream tab from the view issue page.

For those of you commenting about better management of multiple attachments to an issue- we are tracking that improvement via JRA-5351

Hello All,

Based on the wiki approach to outlined in this issue I have update JIRA code to help in associating comments with file attachments.

The details are below.

Thanks,
Ganesh

Steps:
1. Ensure 'Wiki Renderer Macros' plugin is Installed.
2. Ensure that the 'html' module is enabled
3. Ensure that the 'comment' field uses Wiki Sytle Rendering
4. Compile 'AttachFile.java' & Replace at atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/issue
5. Compile 'AbstractCommentableIssue.java' & Replace at atlassian-jira/WEB-INF/classes/com/atlassian/jira/web/action/issue
6. Place clip.gif in atlassian-jira/images/icons

Usage:
1. Attach File / Screenshot
2. Enter comment & submit.

Issues
1. When a file is deleted the wiki tags are shown in the comments section.

Files:AttachFile.java,AbstractCommentableIssue.java,clip.gif

Hi,
Could you please let us know if this functionality is implemented in any Jira version?
If Yes, how can we turn it on?

fyi..
We are running Jira version '3.11 Enterprise edition'.

Thanks,
Abhishek

I prefer Chris's implementation. How long will we have to wait for this? Here is another simple improvement, with lots of votes, that has been out there for ever. How about knocking some of these little ones out and giving them to us. Please!!!!

Yes Dmitry, I agree with your comment, Attachments need descriptions.

Comment preview available on the right hand side of the add comment box (next to wiki help). Will show how wiki markup in your comment will display after you publish your post. It is useful to check that all that bold text or image thumbnails do what you intended and don't just render as funny symbols in the text.

Excuse me, what is the comment preview feature and how does it works?

Also, it is necessary to apply a short comment for each attachment. Especially when attachments have the same name. Like this

As well as ! attached-image.gif ! already mentioned.

! image.jpg|thumbnail ! is also very helpful here as well as [^attachment.ext].

gnome-about-logo.png

Using the comment preview feature avoids embarrassing slip ups!

Of course this could all be done automatically by Jira, which would be much easier. And it doesn't avoid unlabelled attachments at the top of the page.

Could somebody from the Atlassian team kindly provide an update on this.

Thanks,
Ganesh

We have made some improvement here

I like Chris's idea above, but would like it to automatically happen. I don't know that I would want it to display the attachment, but would like a link to open the associated attachment to the comment. It is asking a lot for the common user to know / remember the coding to do this.

As far as the images/ attachments, use a small icon like the preview button next to this comment box when you are adding next to each image. When you click it, then go to the right comment using anchors. This is probably harder to implement, but the one about having the link to the image auto embed in the comment should be really, really easy.

seems to me that there are quite diff. use cases here that need diff. options/processes supported by the UI. is there a wiki page that sums this up? or how do we know how this is going to be impled?

Maybe when this issue reaches 200 votes, then Atlassian can fess up that they are not going to do it...
(meow! haha)

I've also added my vote for this.

I think that part of the issue is that attachments are treated as an Update event, which while I think is suitable for file attachments, does not quite fit for image attachments. This problem is particularly evident when using email listeners, and users send multi-part emails with embedded images.

My suggestion for this would be to default or provide an option to automatically inline the image attachment with the comment, much like the wiki notation provides manually.

I added a vote for Polycom. We had originally opened a different issue which is really a duplicate of this one.

I know that Atlassian is always looking for ways to chunk up features into smaller, more doable ones in point releases. So on that note... one of the ways this mish-mash of new/outdated attachments and comments could be helped (until the issue is implemented as requested – with accompanying comments) is simply to move the "Manage Attachments" grid to the main issue view page – so it's right there and visible . This would give a better overview of all attachments . But then you also need to make the columns sortable – e.g. Date Attached, which is especially helpful to provide clues for users looking at issues with many many attachments (yes, we have those)

One aspect of this is that often a fix will be attached to an issue, only to be superceded by a later fix, or added to be similar fixed for different product versions. It would be great to have the option for an inline comment with the attachment that displays on the attachment screen, so one could say things like "use this one" or "outdated, don't use" or "for version x.y.z" right next to the download link. Another nicety in this context would be an option for non-admins to mark an attachment as stale without removing it, so it appears greyed out, and becomes immediately recognizable as the wrong download link to click.

I see this inline comment as independent from a longer comment that may or may not be attached to an attachment, and that would appear within the regular comments section. In such a larger comment I would still like to see a direct link to the attachment it was created for, as others have requested here.

It would be really handy when a support ticket contains several attachments to allow them to be sorted by date, name or size - add extra customisation.
Further, I would welcome the option of having attachments associated with a particular ordering schema - attch 1 comment B etc... using anchors or a numbering mechanism.
Presently it is really difficult to distinguish the association of a particular comment made on issue and an attachment linked to that.

Definitely confusing the way this works. I'll often document a hardware bug with 20-30 images showing different stages of a strife test. The images do not appear in the order I post them, nor next to the comments I include, both of which make it quite difficult for others to sort through my posting. Please fix!

But, as you discovered, thats pretty hard to get right first go

The automatic association (and potential inlining) of attachments with their comments sounds like a great improvement.

Of course, you can always explicitly link an attachment with a comment, using the wiki renderer notation !attachment-name!

Attachments should be organized and related to their "add" comment.

The current implementation leaves attachments as a grab bag. It is much less useful than other competing product's implementations.

See http://www.fogcreek.com/FogBugz/40tour/04.html for an example of an inline image coupled with its comment.

A screenshot really is just a comment of sorts (a visual comment). It seems reasonable to show the screenshots under the comments section with the associated text ordered by time.

Looking at the usage pattern, we typically request the QA teams to include screen shots, log files and other artifacts in support of diagnosing the problem.

As such, I would propose, that a comment be allowed to have multiple artifacts associated with it. Furthermore, in associating an artifact with a comment, one may provide additional context (comments) to the artifiact.

In short, I am proposing to allow multiple artifacts with a comment, and allow sub-comments.