Importing project archive fails if referenced job name/group changed

[ProTip]

Describe the bug
Projects with jobs referenced by UUID that have had their names or groups updated will cause import failures with "Preserve UUID".

My Rundeck detail

• Rundeck version: 3.0.13
• install type: Docker

To Reproduce
Steps to reproduce the behavior:

1. Import the project into one instance
2. Rename RefMe or its group
3. Export the project and import into another Rundeck instnace
4. See error

Expected behavior
Rundeck should continue to allow me to export and import projects even if I have renamed referenced jobs or their groups.

Screenshots

Additional context
The error message does not explain the problem or offer a workaround. The logs are the only indicator of the issue:

2019-02-04 22:48:45.258 ERROR --- [tp2031149831-30] rundeck.services.ProjectService          : Failed loading (1) jobs from XML at archive path: rundeck-ProjectA/jobs/job-a6d88d66-920b-492b-b7c4-1a22da67333b.xml
2019-02-04 22:48:45.259 ERROR --- [tp2031149831-30] rundeck.services.ProjectService          : Job at index [1] had errors: Validation errors: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]]; Invalid Option definition: Foo: Workflow has one or more invalid steps: [1: [Job Name does not correspond to the UUID]]

ProjectA-20190204-225828.rdproject.zip

[gtsteffaniak]

We are running 3.0.13 as well and noticed the same issue on import via:
rd jobs load

:Workflow has one or more invalid steps: [2: [Job Name does not correspond to the UUID]]
Validation errors: Workflow has one or more invalid steps: [2: [Job Name does not correspond to the UUID]]

This is because the job name or group has changed. Although, this is still a bug since it should not be an issue if the UUID exists.

        <jobref group='PL1/Ready for Market/On Demand' name='On Demand - RDFD APAC Shanghai (SSE) Ready for Market Check' nodeStep='true'>
          <arg line='-arg1 External -agr2 65189d4ta' />
		<uuid>b16a84e1-758a-4c6f-8d98-93f6e4a43520</uuid>

Stripping the UUID line allows for the import, but even after importing, the job still errors when trying to reference a corrected job name.