Issue Summary

If a user makes an amendment to one, or more, of the fields that does not auto save and then follows this by making a change to the Title, when they click the mouse outside of the Title field, then the field is briefly  highlighted in yellow and a green pop-up box indicates that a save has been performed by stating "Updated Successfully

This green pop-up might cause the user to believe that all their changes have been saved and if they subsequently close the details for the feature  panel without clicking Save,  any data changes (which might even include text in the description) will be lost 

This issue  is potentially made more difficult  as users are unaware of which fields might automatically save and which won't. The Title, Acceptance Criteria and Description fields can all auto save (although the auto save of the Description field does depend on the setting for Jira Text Formatting Type)

While this issue was found against a Feature it is possible that a similar issue may affect Stories. 

Steps to Reproduce

Note: as the reporting customer found this during an investigation into when Features can be saved if the Product field is not set, the screenshots in these steps are based on using a Jira Integrated configuration and not setting a Product in the Feature. The problem behaviour can be seen with or without setting a Product (although if Save is clicked without setting a Product then the result is a Red Pop up-message.)
All screenshots came from a test environment within Atlassian. 

1 - Make sure that Jira Align > Administration > Jira Settings > Jira Setup > Jira text formatting type is set to HTML - This disables the Automatic Save of the Description field

2 - In Jira create an Epic in a project that is integrated to Jira Align

3 - Wait for the feature to be created in Jira Align, it should look something similar to this:

4 - Change the text in the Description and adjust another field (for instance the Program Increment) and DO NOT click Save. It might now look something like this:

5 - Now change the title of the feature

6 - Click anywhere outside the title in the details panel, the field will save, be briefly highlighted in yellow and the green pop up will be seen

7 - Without clicking Save refresh the screen - the change to the Description and the PI will be lost

Expected Results

There should be no way for a user to see a pop-up indicating changes have been saved when only one field is actually saved. As it is the perception that all their updates have been saved that might lead a user to not click on Save.

Suggested solution behaviours include:

• Stop allowing individual fields in Features and Stories to Auto Save - always require the operation of the Save button which will Save all changes (possibly the preferred option for consistency as most fields do not automatically save updates)
• Change the AutoSave so that when it happens all field changes are saved (with a subsequent red pop-up failure if a required field is not set)
• Change the pop-up box so that it indicates only 1 field has been updated successfully (and name the field) - make this box stay on screen for long enough to read it.
• Change the pop-up box so that if other fields are pending a save then the colour is different and these other fields are listed in the box (at the same time make sure this box stays on screen for acknowledgement and possibly show a Save all fields button. )

Actual Results

Changes made to the non-autosaving fields will be lost

The end user may be unaware that their data has not been saved and it may be some time before any missing data is noticed. 

Workaround

Always click Save  (or Save & Close) just prior to closing a details panel, if you have made deliberate changes, and even if you have seen a previous message indicating a save has taken place.