In one of our Service Desk projects when you comment on an issue there is an Attachments button on the toolbar of the comment box. You can click it and choose to attach a file to send to the customer.
In that same issue if I click a workflow transition button the comment box on the screen that comes up does not have the attachment button in the toolbar.
In a different project that button is there when I use the exact same screen. I've checked all the permissions I know and I can't yet find the difference or why this button wouldn't show up in one project but it would in the other.
The primary difference between the two projects is that the one the button appears on the toolbar of the screen, is one that was created as a Business project type with the Project Management template but was changed to a Service Desk project later. I have compared screens and field configurations and they all seem to match though and can't find a setting that governs the comment box.
They do, I'm testing this as a jira-administrator with project lead and project administrator roles. I can attach files just fine.
I've done a little more testing and confirmed that when I setup a project with the Business type -> Project Management template that button will appear on that screen.
If I setup the project as Service desk type -> IT Service Desk template the button will not appear on that screen but it will appear on the comment box for the issue like in the original screen shot.
I've also made sure the comment permissions and attachments permissions are identical between the two projects.
It is, both projects have the attachment field in the Edit Issue Screen. I've also made sure they were using the same Field Configuration scheme. The Project Management project was using the System Default Field Configuration so I changed the Service Desk project to match that and reindexed as a precaution, the button still doesn't appear in the comment box toolbar. Both the original field configuration and the System default both use the Wiki Style Renderer for the comment box.
This is all incorrect. I have just found out why this kept happening.
It's impossible to add a comment WITH an attachment UNLESS the ticket already has a file attached.
This happens because the Attachment button is only shown as a convenience list to pick existing attachment.
I reckon this is a bug, and the Attachment button should ALWAYS be rendered, even when no files are attached to the ticket.
Doing so will ultimately allow people don't have to navigate away, or get distracted, when they need to add an attachment to their comment.
I am facing the same issue.
I have created a multi line text field and changed its Renderer to Wiki Style Renderer.
When I try to create the issue in the same tab and the Create Issue screen comes as a pop up in the same tab, the attachment button is VISIBLE, but when I try to create issue by right- clicking on the Create button and choosing option: Open in a new tab, the attachment button is INVISIBLE. I am trying this with jira-admin id and it has the permission to add attachment and system field Attachment is added in the screen.
Any help would be appreciated.
Same issue here!
We face same issue.
When there is no attachtment yet in the ticket, and we want to close with comment + attachment we need to go back, upload the attachment and then close - with comment and attachment;
All because the Attachment is NOT visible in the comment screen MARK AS DONE.
(Im admin - with all rights)
Like to have this fixed as well @jiraservicedesk
Same as a normal comment under activity... the screenshot shows what we need!!
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events