When the issue arrive to certain status I need to lock fields and actions to agents and when it changes the status who doesn't have those properties, the issue must be editable again.
I have this list of properties:
jira.permission.link.denied
jira.permission.comment.denied
jira.permission.edit.denied
jira.permission.modifyreporter true
jira.permission.work.denied
jira.permission.editable.assignee true
jira.permission.create.subtask.denied
jira.permission.attachdeleteall.denied
The result is:
The agent CAN link issues - Bad function
cannot comment - ok
cannot edit other fields - ok
The agent CANNOT modify the "Reporter" - Bad function
cannot log hours- ok
can edit assignee- ok
CAN create subtask - Bad function
cannot delete attachment - ok
How can I fix the bad functionalities?
Besides that, when I transition the issue to another status that doesn't have those properties, the agent cannot comment, and there is not a permission problem.
How can I solve that?
I've made a lot of test and still cannot figure out how to solve this.
Cannot log hours but can edit Original estimate
Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨
Join the EAP →Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.