You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.
Creating a new EEP sky setting by using an existing setting as a "template" and then using the Save As option causes the edited setting to be saved to inventory using the original's name (producing what appears to be a duplicate). The "new" asset must then be manually renamed from within inventory.
What were you doing when it happened?
Step to reproduce:
Edit an existing sky setting.
Make any changes - colours, textures, whatever.
Select Save As from any tab drop-down.
Click Save As.
New settings asset created with the original's name (fig 1).
User then has to rename asset from within inventory.
What were you expecting to happen instead?
On clicking Save As, would expect a dialogue to be displayed, allowing the user to rename the setting as a part of the Save As process, avoiding the need to subsequently rename the asset from within inventory.
Relying on the user to rename assets after the fact could cause confusion as to which version of an asset they should rename, particularly if they don't have their inventory set to Sort By Most Recent First
[FIXED] [EEP] Save As does not provide dialogue to supply new setting name
Type
Bug
Priority
Unset
Status
Closed
Resolution
Accepted
Labels
whirly-eep
Reporter
Inara Pey (inara.pey)
Created at
2018-09-21T20:24:31Z
Updated at
2020-06-15T15:23:38Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'Date of First Response': '2018-09-28T15:28:40.864-0500',
'Original Reporter': 'Inara Pey (inara.pey)',
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'Creating a new EEP sky setting by using an existing setting as a "template" and then using the Save As option causes the edited setting to be saved to inventory using the original\'s name (producing what appears to be a duplicate). The "new" asset must then be manually renamed from within inventory. ',
'What were you doing when it happened?': "Step to reproduce:\r\n\r\n1. Edit an existing sky setting. \r\n2. Make any changes - colours, textures, whatever. \r\n3. Select Save As from any tab drop-down.\r\n4. Click Save As.\r\n5. New settings asset created with the original's name (fig 1).\r\n6. User then has to rename asset from within inventory.",
'What were you expecting to happen instead?': "On clicking Save As, would expect a dialogue to be displayed, allowing the user to rename the setting as a part of the Save As process, avoiding the need to subsequently rename the asset from within inventory.\r\n\r\nRelying on the user to rename assets after the fact could cause confusion as to which version of an asset they should rename, particularly if they don't have their inventory set to Sort By Most Recent First ",
}
The text was updated successfully, but these errors were encountered:
What just happened?
Creating a new EEP sky setting by using an existing setting as a "template" and then using the Save As option causes the edited setting to be saved to inventory using the original's name (producing what appears to be a duplicate). The "new" asset must then be manually renamed from within inventory.
What were you doing when it happened?
Step to reproduce:
What were you expecting to happen instead?
On clicking Save As, would expect a dialogue to be displayed, allowing the user to rename the setting as a part of the Save As process, avoiding the need to subsequently rename the asset from within inventory.
Relying on the user to rename assets after the fact could cause confusion as to which version of an asset they should rename, particularly if they don't have their inventory set to Sort By Most Recent First
Other information
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: