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
When importing an existing RunDeck job definition in XML/YAML to a new project - if the UUID of the job definition already exists the import will fail.
Functionally it makes sense for this to fail but it would be nice if the import process could remove the UUID from the job definition or at least do so by default when "create new job" is selected during the import process.
The text was updated successfully, but these errors were encountered:
When importing an existing RunDeck job definition in XML/YAML to a new project - if the UUID of the job definition already exists the import will fail.
Functionally it makes sense for this to fail but it would be nice if the import process could remove the UUID from the job definition or at least do so by default when "create new job" is selected during the import process.
The text was updated successfully, but these errors were encountered: