Clone Job - Bad Functionality

Question

Steps taken:

1. Select existing ETL Job (let's call it "sample-job").
2. Clone job.
3. New job created, called "sample-job-copy".
4. Rename job.
5. Hit enter immediately after renaming.

Outcome: New job is saved as "sample-job-copy".

There are so many occasions where I've cloned a job, changed the name immediately (since this can't be changed later) but because of the above behaviour, it has renamed incorrectly and saved itself, so I need to delete it and redo the cloning. I admit it adds less than a minute onto my workflow, but it frustrates me that the service is designed like this.

Please can we have it so that when you do hit enter immediately after renaming a job, it saves the job as the name for whatever's in the name box?

Riku_Kobayashi · Accepted Answer

Hello.

Because this issue is a UI issue, we recommend that you submit it from "Feedback" at the bottom left of the management console screen, rather than posting to AWS re:Post.  
![a](/media/postImages/original/IMwnEDb8hnQYaO1TJaiUg93Q)

![a](/media/postImages/original/IMsqxsafKwTBeWSuwPnfSMqg)

Pandurangaswamy · Answer

Hi

**Suggested Enhancement:**

To improve this workflow, AWS could consider modifying the job cloning process so that when the user renames a job and presses "Enter," the system saves the job under the new name entered in the field, rather than the default name.

**Potential Benefits:**

* **Increased Efficiency:** This change would eliminate the need to delete incorrectly named jobs and re-clone them, reducing disruptions in workflow.

* **Improved User Experience:** By addressing this behavior, users would experience a smoother process when cloning and renaming jobs, especially in scenarios where job names are critical and cannot be changed post-creation.

* **Aligns with Best Practices:** The expected behavior when interacting with form fields and renaming should be to save the updated input value, providing a more intuitive and predictable experience for users.

**AWS Documentation and References:**

For ETL jobs using AWS Glue or other AWS services, it may be helpful to refer to the following AWS documentation that covers job creation, cloning, and editing best practices:

**AWS Glue: Create and Manage ETL Jobs:** This document outlines the workflow for creating, managing, and cloning ETL jobs.

https://docs.aws.amazon.com/glue/latest/dg/what-is-glue.html

**AWS Glue Job Properties:** Provides details on job naming conventions and restrictions.

https://docs.aws.amazon.com/glue/latest/dg/aws-glue-api-jobs-job.html

**AWS Glue Best Practices:** Offers recommendations to optimize the overall job configuration and process efficiency.

https://docs.aws.amazon.com/pdfs/whitepapers/latest/aws-glue-best-practices-build-performant-data-pipeline/aws-glue-best-practices-build-performant-data-pipeline.pdf

**Actionable Recommendation:**

I suggest raising a support request with AWS to highlight this specific functionality concern. AWS frequently updates its services based on customer feedback, and this enhancement could significantly improve the usability of ETL job workflows. You can open a support ticket through the AWS Support Center to request this feature enhancement.

Clone Job - Bad Functionality

Relevant content