I have same issue.  I Try with: triggerIssue.comment.last.body when create a new Message in another project, and copy this message with trigger automatization. But i don't have access to the images. 

When adding an image in comments of a particular issue the image link appears in the comments instead of the image getting displayed. how to remove the image link and display only the image.

Oh.... Thumbnails instead of inline pictures is ugly/awkward, and I am pretty sure not delivering experience the majority was hoping/looking for. Is there a continuation elsewhere?..

Related to what 51a1a92a7a5a is mentioning (JRACLOUD-80640, with any attachment, new or existing, in new issue view, there is no way to format it as a true thumbnail so that it sends out to Jira Service Management customers as a thumbnail and not a massive image. We really need to be able to tag the property of the image to be a thumbnail, no matter how it is added.

This bug is still happening for all large images: JRACLOUD-75857 Images Added in New Issue View Comments Show as Full-Sized in Jira Emails

And then we also still cannot add existing internal attachments: JRACLOUD-80457

Only if they were already public. 2239430e27fb, can you address when these pieces will be fixed?

It´s good, that you tried to bring this functionality back, but this is not a good solution.

When you try to add a attachment inline (e.g. in a numbered list) the attachment is added as gigantic icon (issue one) below the numbered list, instead inline (issue two).

Hi Everyone, 

I’m Ahmud, a product manager working on the issue view in Jira Cloud. Thank you for sharing your votes and comments for this feature request. We have launched this to 100% in Jira Cloud. You can find out more in this community post. 

If you have any questions or feedback, leave us a comment in the section of the community post. We’d love to hear what you think about this new feature.

I'll be closing this ticket now. 

Ahmud 

I can confirm, I have two accounts in two different regions, only one of them has the option 

It took me a minute to find the option, but for me it is showing up now.

As you are typing a comment, you type "/" then start typing the word "attachment" then the "Attachments on this issue" option becomes selected.  Selecting that option opens up a dialog with a list of files attached to the current Jira ticket.

Hey folks, I don't know if I misread some things, but for us this feature is still not visible
We are on EU servers, may this be the reason?

...I'm a little at a loss for words here. First: Yes, with Jira cloud you can now "include" (formally) attached files in the descriptions/comments via a attachments macro. Nice. BUT, although an attachement is an image, you can't edit the appearance as you can, when uploading it the very moment you "include" it in the description/comment. So if you want to show it properly (visible) within the description, you still have to upload it while editing/writing using the "Files & images" macro.

That is - again - an impressive showcase on how to break with existing (I'd guess "working and accepted") UX.

After the extended development time I figured the team was working on something big … 🤔
An immersive audio/visual experience.
A framework allowing me to explore a generated universe based on my journey.
A world showing me what the true meaning of the selected issue really is.
Revealing the motivations of other commenters and how I can best reach them visually.
A labyrinth of my own beliefs, fears, and darkest secrets that amplifies my visual thinking.
At once, all that I know and all that I've forgotten about product development.
A place that made me a better communicator. A better person.

Instead, I got a slightly kludgy image picker. Cool.

This is mentioned in https://confluence.atlassian.com/cloud/blog/2022/12/atlassian-cloud-changes-nov-28-to-dec-5-2022 - with the remark "ROLLING OUT". Thanks for bringing that to our attention through this issue.

We don't have it yet in our environment, but seeing others have it already tunes me positive! Since tomorrow its Nov 6th, the anticipation of having such a stupid (re-added) feature makes us hyped.

Now lets finally hope that we get the "new editor everywhere" issue fixed, because its a pain to constantly be confronted with the "old markup" and having to use

 here and there still.

Works in our cloud Jira already, hopefully those links work for a preview for anyone who is interested

1. edit comment
2. choose attachment

@Stephen Avery  I've just checked and /reference doesn't appear in my cloud JIRA, so maybe it's a plugin of some sort, or it's on a limited roll out at the moment

I seem to have this ability now in Jira Cloud - I'm not sure if this has been rolled out for everyone, or if it's a standard feature (I'm not our Jira administrator so I don't know we have added a plugin etc. which has given us this ability, rather than a change from Atlassian themselves?)

When I go to add a comment, I get a hint to type "/reference" to insert an existing attachment. Typing /reference then gives me a prompt to choose an existing attachment. Clicking this then gives me the option to choose from a list of previously attached files. Selecting a file and clicking 'Insert' then inserts a link/thumbnail of the attachment in the comment.

I thought I'd add this here and explain it in detail in case this has been introduced by surprise and others who have been waiting for this change for ages are unaware.

Edit: I've had to remove pictures from my comment as although Atlassian's Jira inserts them into the comment, it doesn't allow me to attach them to the ticket, so they can't be viewed.

When is the "Launch" guys? A whole year for a pretty simple feature which was part of the old product is just too long. 

Aakif - nice point! Waiting for "Launch"...

So removing a feature and restoring it is considered as a Launch now?

I totally agree with faaf07aed137. There should be some timeline mentioned. 

Thanks 2239430e27fb, I'm waiting for this fix since long. Please keep us posted. 

Thank you 2239430e27fb 

I also agree with faaf07aed137

Hi Ahmud,

Thank you for the update it's great to hear that this is being worked on.

If there are any opportunities for input / feedback on these designs please let us know.

As discussed extensively in this thread, communication around these features is extremely poor with official communications from Atlassian having gaps in the YEARS metric. As a good practice behavior, can you please commit to providing a due date for further updates? I don't even care if there is no progress to communicate, it would just instill some confidence to the community that features are still owned and alive.

Hi Everyone,

Product manager on the issue view here. Thank you for your patience and feedback on this feature. We have completed the designs for this feature and are currently in development. I will post an update once we launched the feature.

The claim that "For now you can still temporarily click through to the old view to reference attachments in the old view" is not really true, because even when you do that, once you view it in the new view again (which everyone does) it will break the layout you added in the old view.

For example if I add 

!myimage.png|height=250,width=250!

in the old view the extra attributes will apply, but when I view in the new view those will be gone and Jira will have changed the size of my image from the original size for no apparent reason and I can't seem to change it.
The new view's image layout CSS also changes what it looked like when I added it in the old view, and there isn't a way to get it exactly like it was with the new view.
Also, then when I next edited in the new view the image markdown wasn't there and when I saved the image was gone.

So there isn't really a workaround that actually works.

Hi @Pujanito,

thanks for taking this new approach! I also thought about this and decided to contact the Atlassian staff through Twitter: https://twitter.com/JohannesRabauer/status/1580423641157640193

Their reply:

Hi Johannes, appreciate you reaching out. We're still working on a solution to referencing an attachment that has previously been commented on an issue. So far, we've completed the user testing & plan to provide an update to the ticket closer to the release date. 

That was almost two weeks ago.

Hi everyone,

Since not responding to users' and admins' concern is weird and not very "Atlassiany" (at least the Atlassian I knew), I fear no-one at Atlassian is getting notification on the votes and comments here. Otherwise someone would have reacted. So I'm giving them the benefit of the doubt and consider this a technical issue. Otherwise ignoring over 1600 people's frustration would be super unprofessional.

That is why I submitted a support ticket with this text.

If you are an Atlassian Admin and can submit a support ticket, please go to support.atlassian.com and ask what is going on and when we can expect this "high priority" issue be resolved and released. Maybe peer pressure will culminate in this ticket getting finally resolved.

Here is a text, in case you want to copy/paste.

Cheers.

Hello,

There is a very old and critical bug (or missing feature) that has been inactive since over a year, instead of technically being in "In Progress" status.
_https://jira.atlassian.com/browse/JRACLOUD-72208_
Atlassian has noted over a year ago, that this feature has a "high priority" and they are on it with full power, since it was available in the old issue view, and forcing users to use the new issue view without providing them with all the functionalities comes as morally questionable and technically incompetent.
My question, and the question of over 1060 people who have voted for this issue is: what is happening? Why is this ticket "in progress" with high priority since over a year, and why is there no progress and no announcements on why the users and admins are kept hanging?
Please get in contact with whoever is in charge of this ticket and provide an update so that we know what to tell our clients. This is not a good look for Atlassian.
Thank you in advance and all the best

Wow. No, not the good kind of wow.

So the Old School view (suggested workaround) isn't an option for my team-managed projects.  So ... hmmm.

Amazingly, I can't even seem to click on the file attachment, right-click to get a good URL for the file, and past its url into the text of a comment.  Wow.

In team managed project, I'm considering using a workaround that involves the use of this text:

"About the file I just mentioned in the comment ... no, I can't give you a handy link to open it. 
Why?  Good question.  Here's my best answer:  Atlassian has been "delayed" in fixing the ability for me to link here directly to the attachment that I'm wanting to so handily point to you to. See this posting for more information.

By the way, people, they've been working on it for multiple YEARS, so I really don't want to hear any more complaining when I can't get a high priority bug fix resolved in multiple days.  Anyhow, go up to the attachments area of this issue and look for the file named [insert_filename_here]."

Yes, this text is ridiculous ... yes, it makes management wonder why we're using a product that doesn't make it easy to do things that they think should be easy to do, and that they expect that I, a non-programmer, could have fixed in a day.  

Multiple years to fix this ... wow.

75f3e0bc41b1 it is still in Cloud too (just buried in the Old Issue View.... which maybe you are using Team Managed projects and are trapped).  I find myself switching back to grab an existing attachment.

We also have added the attachment field to some transition screens so that we can copy/paste an attachment into the comment on that transition (that works in the New View).

Maybe these tips will help others with some use-cases while we all wait.  I'm not really sure what the blocker is here and why it wasn't considered a valid use-case during the attachment overhaul.

Can you please Atlasian tell us the number of votes needed to get this moving forward? because 1029 doesn't look a small number to me

@Yon, it is frustrating and obviously not a good look for Atlassian in the long run. Not giving a f* about users and admins is a disease that most tech companies that get big enough is infested with. Atlassian fans were hoping it takes longer for it to get infected, but alas. Everytime I read an announcement about some irrelevant initiative and investment on diversity or whatever that has nothing to do with their core products and business, and see how many important bugs and features are in the backlog, I feel sick in my stomach.

And to answer your question, obviously Atlassian will pay the price in the long run if it keeps ignoring customers and putting critical "bugs" in "Gathering Interest" for years, or even worse in this case: having an important missing feature with over 1000 votes in "In Progress" for over 2 years.

But the downfall takes years and I can see in my clients that they are looking for alternatives. So my observation is that more and more users are giving up on Atlassian, but until there is a viable alternative, there is no choice but to wait for the right moment the pull out. Until then, we all have to suffer and only hope that they change course.

To add to the previous comments.

Why would Atlassian change anything, if you all still use it, and pay for it.

Andrey, the bigger question is how many YEARS is needed to implement a FEATURE that ALREADY EXISTS in Jira server?!  We've been forced to move to the cloud BEFORE IT IS READY for true, full-featured enterprise use.  It's like Atlassian said, we know the plane is going to crash,  so JUMP now, we'll fix the parachute later (after we "gather interest" on the feature and decide if we'll re-add the ability to "Open" the chute.)

Atlassian, how many YEARS is needed to implement inserting already attached image into comment??

I'm not even mad... I'm just disappointed at this stage.

I don't know what internal hellfire product managers need to go through in order to actually fix bugs and make improvements at Atlassian but the simple lack of communication to your user base is just demoralising and insulting.

To communicate this as being worked on in March 2021 and to say that this continues to be a top priority in October 2021... Unless you can tell us otherwise, is a lie.

Unless you communicate otherwise the user base will believe that you don't care about fixing issues or making improvements (that users are asking for) while continuing to take their money.

This is the Atlassian story so far:

• Customer: I paid for a round wheel, that worked.
• Atlassian: But this square wheel looks so mich nicer. We've made it default.
• Customer: But it doesn't work as well. Can you change it back to the way it worked?
• Atlassian: Yes, of course, we value your input and care about your user experience.
• Customer: Waits 3 years.
• Atlassian: Counts money.

I had a dream...

that Atlassian team started to fix bugs before users give up!

@Ahmud Auleear is there any update on this? Last update was over 1 year ago.

This should be implemented again!

We're recently migrated from server to cloud and we really do missing this feature.

I'll take one of these, please!

Where is this feature????

The feature should be reimplemented urgently!

Without this feature images only can be inserted directly into the text field. The attachment is uploaded automatically, but it is named randomly by Jira.

It would be useful to upload the image first and use it in the text field! Then you have the option to use meaningful names for the attachments. This would be very helpful when there are a couple of attachments.

So, please bring back this feature!

Requirement analysis will be completed by 2074, development will start immediately after in 2086.

By when can we expect this issue to be resolved, is there any timeline/update on this issue?

+1

If the only workaround to do this is to see in the "old view".

Could you enable the possiblity to enable the option to select by default the "old view"? 

If you go to your profuile settings we are not able to switch to go permanently to the "old view"

Best regards,

its so annoying with the new features.

(this should be in another report, but i just want to rant here as it matches the topic: in confluence, i am still stuck creating 90% of the pages with old legacy editor, as the new editor looks great and is nice to use, BUT misses multiple important layout features the old editor had. most noteably: you could add http url images in the old editor, and they where shown loaded directly from that page. e.g. from google docs! but the new editor doesnt support this basic html feature anymore. i mean, common, its just an img src= that needs to be done here, Jesus Fucking Christ. i requesteds this with support in 2019 when the new editor arrived, sure sir, yes sir, that will be done sir, is truly easy.)

Unfortunately images don't display!

Unwatched this issue.

Added image in this comment so Jira can see how that looks...

@Connor definitely agreed. I have a lot of compassion for the situation that Atlassian PM's (and likely engineers as well) find themselves. Hopefully there's enough mindful people high up to help push this shaky roll-out the rest of the through.

Little things like this add up to an experience that no one on my teams is happy with. This is a table stakes for any software product management tool. The forced migration to a lesser feature set, presumably for a "slick UI", is unacceptable.

I hate fighting friction like this when I'm trying to focus the team on product objectives and milestones. Jira and Confluence have become stumbling blocks for every team I've worked with over the last three or four years and it's only gotten worse as all these loose ends are ignored.

I stay on the watch list for this and other similar issues as a reminder to help my customers find something better than what Atlassian has become. I've tried a number of alternatives with success, but Shortcut is the primary contender for me right now.

I continue watching as a daily reminder to care about my own customers as well as have compassion for the poor product managers at Atlassian who probably don't have any say in this matter and appear to be faced with top down priorities as opposed to team-driven priorities

@devlopmentwics, the same reason I'm here. Tired of waiting for this and don't care to follow anymore.

Why would you forcibly transition all cloud users before providing this "TOP PRIORITY" previously supported feature? Makes me want to switch to Microsoft's DevOps

Seriously... March 18th, 2021:

Work on attachment referencing in the new issue view has begun!

It's almost a year and a half later... I've developed this feature in a previous job for an in house system in a few days. SMH

How can i stop receiving e-mails when somebody comments on this issue that is very annoying but is never going to be solved?
"Stop watching this issue".

How can i stop receiving e-mails when somebody comments on this issue that is very annoying but is never going to be solved? 

1) Which user attached the file not showing in new view when moving the cursor over the attachment. This feature is needed in new view

2) In Cloud Jira's new view comment box , the option for attaching the existing file is not available. This feature is needed in new view

3)  In the issue attachments there are fewer options, please check the image to understand the problem. We need all the view in new view screen of Cloud Jira like Server On-premise

+1

: ) +1