nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to allow adding attachments or editing a particular field of closed issue?

Martin Heineman1

I have a workflow that denies editing after reaching a particular status (this is not the closed status), there are several subsequent statuses.

I use the workflow property jira.issue.editable=false for this status. But i do not want to block the whole issue for editing. It must be possible for users to add attachments and edit some fields of the issue even when it is editable=false.

Is there a way to solve this?

Accepted answers

Nic Brough -Adaptavist-

The whole point of edit=false is to stop editing. That's what it's for.

Either remove it, or create a transition from status that goes back to the same status, with conditions to control who can use it, and with a screen that only includes the fields you want to let them update.

All comments

Nic Brough -Adaptavist-

The whole point of edit=false is to stop editing. That's what it's for.

Alexey Studitsky

When status has jira.issue.editable=false property, self transition works for changing standard and custom fields, but does not work for adding Attachment. Attachment does not appear in an issue after pressing transition button.