Rob Fellows created NIFI-16217:
----------------------------------

             Summary: UI - Unsaved Parameter Context changes silently lost when 
navigating to an inherited Parameter Context
                 Key: NIFI-16217
                 URL: https://issues.apache.org/jira/browse/NIFI-16217
             Project: Apache NiFi
          Issue Type: Bug
          Components: Core UI
            Reporter: Rob Fellows
            Assignee: Rob Fellows


h2. In the Edit Parameter Context dialog, unsaved edits are silently discarded 
in the following sequence:

# Open Parameter Context A for edit and change a local parameter (do not click 
Apply).
# On an inherited parameter, use **Go to** to open Parameter Context B (the 
inherited context).
# In Parameter Context B, click Apply.

Only changes made in step 2's destination context are saved. The unsaved change 
from step 1 in Parameter Context A is lost with no warning or confirmation.

h3. Expected behavior

When navigating away from an Edit Parameter Context dialog that has unsaved 
changes (for example via **Go to** on an inherited parameter), the UI should 
either:

- prompt the user to save or discard pending changes before navigating, or
- otherwise prevent silent loss of those changes

consistent with save-before-leaving patterns used elsewhere in the UI.

h3. Notes

Parameter Context updates are asynchronous (submit / poll / delete update 
request) and the edit dialog shows a review/progress UI after Apply. Any fix 
should account for that flow rather than assuming a simple synchronous save.

h3. Steps to reproduce

# Create Parameter Context B with at least one parameter.
# Create Parameter Context A that inherits from B.
# Edit Parameter Context A, modify a local parameter, and do **not** Apply.
# In the Parameters table, open the menu on an inherited parameter and choose 
**Go to**.
# Observe that navigation proceeds immediately to Parameter Context B with no 
prompt.
# Optionally Apply on B, then return to A — the earlier local edit is gone.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to