trying out your plugin and finding it very useful. Great work!
Currently using it for Acceptance Criteria and DoD lists and found out by accident that although I've restricted who can edit checklist anybody can mark/change item status. I went through the documentation and found out that that's a "feature" - it is only possible to restrict who can edit the items in the list, but not also to restrict who can update their status -> checked/not checked (last paragraph in https://okapya.atlassian.net/wiki/display/CHK/Editing+a+Checklist).
I was expecting those settings would also "cover" status update permissions.
If something like that would not be a good solution then I sugest adding additional configuration options to restrict who can update item status - similar to permission configuration that is currently available for editing items (ie. something like "Assignee Can Change Items Status", "Items Change Status Roles").
We have a setup where issues can be closed only when all the mandatory DoD items are checked, but that's kinda pointless if anybody can check them.
We have a "In verification" status and the idea is that only the current assignee or somebody with "Project owner" role can check DoD liste ie. verify the issue and then close it.
I'm guessing we're not the only one who would benefit from something like this.
Another week, another Topic Tuesday! Agile has been on my mind a lot lately because I've seen good implementations and bad implementations, but now as a Jira admin it matters more to me whether...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events