Cannot Add to Sprint due to - This issue cannot be edited because of its workflow status

[Klaus Foerschl]

Hello.
In one project we are dealing with std. Jira items Story/Task/Subtak and are used to organize work in Sprints, using different boards. So far all well.

No we introduced a new issue type (Change Note), which have to follow a much more restrictive workflow, which allows transitions and modifications (only particular fields by special screens) only to particular project roles at particular issue states.
Since we cannot simply disable the "Edit Issues" from within the project Permissions settings - that would impact the handling of the std. issues types as explained above - we designed the workflow for the Change Note issue types in a way, where most states (except the initial one) have the "do not edit flag" (property).

In order to being able to see Changes Note's in the Backlog, we mapped Change Notes states to std. board states (To Do, In Progress, Done). Now we find our Change Notes in the Backlog.

But, if we now try to add such a Change Note to a Sprint, we get the message "This issue cannot be edited because of its workflow status".

Even if we do not 100%  understand, why Jira is talking about "editing" in this case, we hope there's a solution for us, to deal with our Change Notes in sprints.

I hope i was able to make myself clear and there's someone out there who can teach us how to make it work.

[Steven F Behnke]

In order to add a Change Note type to a 'Sprint', Jira edits a field called Sprint, on the issue. Since you've disabled Edit Issue permission, this fails. I haven't thought of a helpful suggestion yet.

[Klaus Foerschl]

That makes sense, Steven. Thanks for the explanation.

But, still the question is, how can i avoid free editing of an issues type, without marking the restrictive workflow statuses as non-editable.
As already mentioned, denial of edit issues permission on project level is not desirable since other issues types need to be free editable.

[Steven F Behnke]

I do not know of a way to accomplish this. I cannot think of a suitable workaround.

[Klaus Foerschl]

No problem, Steven. I didn't want to only address you by my last question.
So everyone is invited to make suggestions.

It just right now came to my mind, that i could do the following.

- revoking editing permissions on Project Level
- add a new transition "Edit" on every status (STATUS-X -> Edit -> STATUS-X)

BUT. While i'm typing ...
This does not solve the Initial issue, that issues which are not editable - for whatever reason (either by permissions or by status properties) - can't be added to Sprints by simple drag and drop within the backlog.