Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×At the top of the new issue view there used to be an attach quick-add button. It seems to have disappeared on me and I can't seem to find it. I looked through all the screens in use and attachment is still on them so not sure what I did or how to fix it. The link below shows that it should be there but there isn't any useful information on those pages to remove/add that button back.
I am not sure that it is related but on Jira Server (on-prem) we have the same problem but we noticed that the attachment icon is missing in Description toolbar only if we hit "create" button while viewing Jira boards or dashboards.
If we use "Create" while viewing one ticket, the attachment icon is there ;)
So you can maybe try this also on cloud version to confirm that the problem is the same?
I have the exact same issue, and the only solution I have found is to revert the view to the old view. They removed the "Edit" button too for some reason on this new view. I have given "feedback" many times now over the deficiencies of the new view, but they have never reached back out to me to ask about it (even though I have agreed to being contacted when submitting feedback).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, same issue.
But I understood that the "attach" button has been remove from the new issue viwe by Atlassian.
Can someone confirmed ?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have recently come across this same issue. I have 2 Software Projects with very different behaviours:
When I added the Attachment Field to the Screen for Project B the Attachment icon returned to the top of the Description field when creating a new ticket.
This is very odd behaviour as both projects are set up the same and share a Field Config Scheme, yet they are getting different options. Which is concerning when there are supposed to be fields that are default as standard across all Jira Projects to avoid this exact type of behaviour.
This has only started happening in the last week after a recent apparent update from Atlassian as we have had messages noting that things have been added to our Cloud instance.
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.