Summary

When changing the context of a field, all issues associated with that will have the field updated (e.g. removing a project from a field context will set the values for that field to none).

But when such modification occurs, and a user is editing an issue (or simply click on Edit without reloading the page for that issue), the history will create an entry as if the user had set the value of the custom field (whose context has been modified) to none.

Environment

Jira Cloud

Steps to Reproduce

1. Create a field context in a custom field, pointing to a specific project:

2. Set a value for that same custom field in an issue from the referred project. Leave it's view page open;
3. In a new tab, edit the custom field's context, removing that project from it:

4. Go back to the issue view page of the previous issue, but do not reload the page. Click on Edit, and edit the value of another field. Update, and then check the history entry:

Expected Results

The entry should not include an update made to the custom field whose context was modified, as it can be misleading.

Actual Results

Jira creates an entry as if the user had edited the custom field's value.

Workaround

No workaround at the moment