For a customer, we need to block editing the issues in certain stasuses. In order to do that, we add jira.issue.editable = false to step properties.
However, this solution also blocks creating subtasks. When we remove the property, the user can create subtasks because he/she has the required permission. However with the property, they can't even see "Create Subtask" in the menu.
Is this a known problem? If it is not a problem, how can I prevent users from editing on some statuses while allowing them to create subtasks?
It's not so much a "known problem" as "designed that way". The flag for "can not edit" is intended for issues that are supposed to be frozen or closed, and if new data is to go on them, they really should be moved to another status. New data, by definition, includes sub-tasks.
I suspect your only option here is to re-open the issues. I'd consider having a workflow transition with an automatic "create subtask" type post-function on it as well (depends on your exact process as to the best approach)
I think it's more of a logical thing than a technical one. Usually when you close off an issue, you don't want people updating it - you want them to explicitly say "ah, there's more to do here" and re-open it. To my mind, adding subtasks are that sort of activity!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG