I have configured the system so that members of the jira-users group are allowed to create issues in our JIRA setup. Now, my goal is to ensure that those same users can edit an issue only when there is no work log registered on it. I am trying to determine whether JIRA 4.4.x supports such a permission-based restriction. I need advice on configuring this conditional edit access based on the absence of work logs. Any guidance or workarounds would be greatly appreciated.
i dont think jira 4.4 supports that nativly; try using custom plugin or scripting workaround. might need to experiment with groovy scipts to enforce the rule on work logs even though its not built in
Based on my experience, trying to impose conditional editing rights solely based on the work log presence in JIRA 4.4.x is not a straightforward configuration. I encountered similar limitations and had to rely on custom development. In my case, implementing a plugin with scripting capabilities became necessary to intercept edit operations and verify work log entries. It required moderate effort to integrate and maintain, but it indeed provided the necessary control. This approach also revealed that in older JIRA versions, custom plugins often play a crucial role in overcoming built-in permission restrictions.
I have experimented with similar restrictions in a legacy JIRA instance. In my experience, the default functionalities do not support conditional editing rights based on work log entries. Instead, I had to develop a custom event listener combined with a script that checked for work log data during issue updates. This solution, although not straightforward to implement, allowed us to block edits on issues that had recorded work logs. Although it required maintenance and some additional testing, it ultimately met our needs without needing to upgrade to a more recent JIRA version.