In the Edit Issue action, changes made to Additional Fields (like modifying or adding a JSON snippet) prompt Automation to indicate unsaved changes, even when there aren't any.

XMLWordPrintable

    • Severity 3 - Minor
    • Jira Software

      Issue Summary

      In the Edit issue action, when we go to Additional fields only and make any change (e.g., modify or add a JSON snippet). Automation continually prompts that there are unsaved changes even when there are none. Re-saving makes the button reappear momentarily, but it disappears again upon interaction.

      Steps to Reproduce

      1. Shared the screen recording to reproduce the issue.
        1. Screen Recording 2025-03-27 at 6.42.10 PM.mov

      Expected Results

      Ideally, once the Edit issue action is saved, the action menu button should remain visible and functional. It should not falsely indicate unsaved changes when no further edits are made.

      Actual Results

      Automation continually prompts that there are unsaved changes even when there are none. 

      Workaround

      • When we select a field to set, such as Assignee or any other field, it remains Saved and doesn't show unsaved changes.
      • Another workaround is to select any other rule component (e.g., the trigger) and then attempt to update / publish the rule changes.

            Assignee:
            Unassigned
            Reporter:
            Harpreet
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: