you can see in my screenshot in the message, the add image or file is greyed out, and it also doesn't let me copy paste it in:
Hi Abilash,
From your screenshot it looks like you are editing an existing internal note, not adding a new one. I tried the same on my site (Jira Service Management Cloud) and the Add image, video, or file button was active for me, so editing alone doesn’t block it.
My guess is a permission. Attaching files needs the Create attachments permission in that space, and pasting an image is also an attachment. I couldn’t test it without that permission.
Could you check whether the button works when you add a new internal note on the same work item? And could you tell me whether you can attach a file to that work item at all?
Hola Abilash,
I came across an Atlassian issue that might be particularly relevant to what you're experiencing.
JRACLOUD-98779 documents the "Add image, video, or file" button becoming greyed out when attachments are disabled in a project's configuration.
What's interesting is that Atlassian identifies several configuration elements that can affect attachments, including the project's permission scheme, field configuration, and whether the attachment field is available on the relevant screens.
I'd recommend having your Jira administrator verify that attachments are enabled at the system level and that the attachment field hasn't been disabled or removed from the project's configuration.
Since you also mentioned that copying and pasting images doesn't work, this seems worth investigating before focusing on browser-related troubleshooting.
One thing I'd be curious about is whether this happens across multiple projects or only within this particular service project. If it's isolated to one project, that would make its configuration a particularly useful place to investigate.
Thanks,
James
that same option add or attachment is working in other projects, according to my search Issue Status / Workflow Restrictions: In this project have this in closed status properties.
Thanks for the response. As checked, the tickets that are closed—that option is greyed out in all projects. In workflow no properties in closed status.
I could reproduce it now. On my site a closed request in a space that uses the default “jira” workflow has the Add image, video, or file button greyed out in the comment editor. A closed request in another space, where Closed doesn’t block editing, has the button active.
The difference is the status property jira.issue.editable = false on Closed. The default Jira workflow has it, and on my site the JSM Incident and Problem workflows have it too, which would explain why you see it in all projects.
There is an open suggestion for exactly this, https://jira.atlassian.com/browse/JRACLOUD-78326 . The workaround there is to replace that property with jira.permission.edit.denied (empty value).
Could you check the properties on the Closed status itself, not on the transition into it, in the workflow that this work type really uses? If it is the default workflow, you would need a copy of it to change anything.
thanks, that helps, and it means my permission guess was wrong.
If the Closed status has jira.issue.editable = false, that explains it. With that property comments still work, but files can’t be added in the comment editor.
Atlassian has an open suggestion for exactly this, https://jira.atlassian.com/browse/JRACLOUD-78326 , and the workaround listed there is to remove jira.issue.editable from that status and add jira.permission.edit.denied with an empty value instead.
i didn’t test it myself so it is not verified.
I checked all the projects; they have their configured workflow, but in this space the request type has taken the default Jira workflow . So the Add image, video, or file button is greyed out in the comment editor.My question is if we change the workflow from the default to the configured workflow, will all the tickets be affected?
Hello @Abilash
Yes, changing the workflow will also impact the existing tickets that use that work type. Jira may require status mapping if the workflows are different. You should avoid replacing the entire workflow just to get attachments right.
A safer option is to copy the default workflow and replace jira.issue.editable=false with jira.permission.edit.denied (empty value) on the Closed status. Atlassian documents this workaround here: https://jira.atlassian.com/browse/JRACLOUD-78326 Test it first and see if the workflow template is being shared across other projects.
Cheers, Arek🤠🧙♂️
If the add image or file button is greyed out and pasting images fails too, Jira usually isn't letting you upload files at all. It's rarely about the internal note itself. A Jira admin can check these:
Doc: https://support.atlassian.com/jira-cloud-administration/docs/configure-file-attachments/
Hi, thanks for the response. The default workflow is shown as readonly, with no option to edit. Are there any possibilities to change?
does it happen on reply to customer too, or only on internal notes? if its both, id check the create attachments permission for your role in the permission scheme first. if its only internal notes it might be a browser thing, so a private window would be my next try before going to support
It is showing both, but for this project, I checked the create attachments permission have but it is showing the same issue to all users in the project; this is only due to the default workflow readonly for this request type.
thanks for checking it, so it really is the workflow as far as i know the default jira workflow cant be edited at all, thats why its read only. what you can do is copy it in the workflows list in jira admin, change the property on closed in the copy, and then switch the work type to the copy in the workflow scheme of that space. since the copy has the same statuses, your existing tickets should just keep their status when you switch
The permission is fine, so we can rule that out.
You’re right that the system workflow can’t be edited. What works is a copy of it.
The copy has the same statuses, so I’d expect no status mapping. Keep in mind that closed work items become editable again after this.
One thing I noticed in your scheme is that only “Onboarding OLD” uses the system workflow. Could you check which work type your closed tickets have? If it’s another one, the property would sit on Closed in that workflow, and those you can edit directly.
my concern is that after changes are done, the tickets or other workflow tickets will be affected in space? This is the major project in our company. Please let me know
It looks like you're new here. Sign in or register to get started.