-
Suggestion
-
Resolution: Unresolved
-
34
-
58
-
Hi everyone,
This is a periodical update on this suggestion. As always, we thank you for raising and voting on this suggestion. We have reviewed this change and we will not be able to implement the next level of granularity of changed values at this stage as previous values are currently not stored. We know that this is important to you and will keep this in "Gathering interest" as we look into improving Audit logs in general. We've already added more configuration events in the recent weeks and will continue to improve coverage of the logs.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Carol Low
clow@atlassian.com
Product Manager, Jira Cloud
Currently the audit log does not include changes done on Custom fields in the Context and options level. For example who/when/what changed in the custom field options for a single select field could be renamed or removed, and this would not reflect in the audit log, causing confusion about who did the change.
Update: the audit log now includes when the options of a custom field are created, modified or deleted, although it doesn't include the name of the option added/changed/removed, yet:
- is duplicated by
-
- Closed
-
- Gathering Interest
- is related to
-
- Gathering Interest
-
JST-603293 Loading...
- relates to
-
- Closed