-
Suggestion
-
Resolution: Won't Fix
-
1,005
-
168
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use Jira so we can continue improving your experience. We have reviewed this issue over the last few days; however, we have no immediate plans to put this suggestion on our near-term roadmap.
Please remember that jira.atlassian.com is one of many inputs for the Jira roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Justin Thomas
Product Manager, Jira
Feature Request
Problem Definition
Currently, if a user created an issue, he/she will be able to edit all the fields if he/she has the edit permission as well. Some of the users would like feature to restrict for example, reporter to be able to only edit specific fields from the issue that they created.
Suggested Solution
Add permission in field configuration to allow which group/role allowed to add/edit value to the field.
Workaround
Not a perfect workaround but worth mentioning:
OR
- Workflows can be used to achieve it by adding the restricted field on a transition screen. Only specific people can be added to permissible groups who can use that transition. This is explained here
- is duplicated by
-
JRACLOUD-69848 Create a custom field with an edit permission apart from what is set on the permission scheme.
- Closed
-
JRACLOUD-71197 Custom Field management permission
- Closed
- is related to
-
JRASERVER-62157 Allow specific group of user to be able to edit only specific fields
- Closed
-
JRACLOUD-34335 Separate Custom Field management permission
- Gathering Interest
-
JRACLOUD-78839 Restrict editing for custom fields / allow fields to be read-only for certain users i.e field-level security
- Gathering Interest
- is action for
-
ENT-774 Loading...