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; } } }

in the default workflow in closed step the issue is not editable. still I am able to reopen the issue

Flavius Nopcea

One I get with the issue in a closed step the workflow property says that the issue is not editable. that is ok but on the view issue page I can still see the reopen issue button.

why is this possible. the other transitions are not possible which is fine but I do not understand why reopen button is visible. reopening the issue changes the issue status and that is an edit in itself.

is it a bug??

Accepted answers

ConradR

It works as configured. There is a transition from "Closed" to "Reopened":

https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

You could configure your own workflow without this transition. But in my eyes the possibility to reopen issues makes sense.

Maybe you want to add a condition to restrict this transition to developers or admins. (see link above)

All comments

ConradR

It works as configured. There is a transition from "Closed" to "Reopened":

https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

You could configure your own workflow without this transition. But in my eyes the possibility to reopen issues makes sense.

Maybe you want to add a condition to restrict this transition to developers or admins. (see link above)

Flavius Nopcea

so to make sure the transitions from a step do not interfere with the jira.issue.editable = false property?

Nic Brough -Adaptavist-

The property "do not edit issue in this step" is totally independent of the transitions. Think of them separately. The property JUST stops people using the EDIT function. Transitions have nothing to do with it.