Not a major issue by any means but a minor niggle I just discovered that you may not be aware of.
I just noticed that one of my jobs was named with incorrect case (e.g. started with Bir-... when I meant to start it BIR-...). When I edited the job just to rename it (yes, I'm fussy about such consistency it wouldn't let me saying something to the effect of "A job with this name already exists" so I had to change it to an interim name (BIIR-...) then back to the desired name.
Minor bug but still a little annoying as I'd expect the interface to be aware that I'm editing the job in question.
(Posted in the tape board simply because it happened to be a tape job but assume same behaviour for all jobs).
I have not managed to confirm that in my lab. Do you mean that editing the job's name from, let's say, "Name1" to "NAME1" gave you an error stating that "NAME1" job already existed whereas you don't have one? If do then I suggest you to open a case with support so they can confirm the described behaviour.
To add a very similar little niggle, when renaming a job in a similar fashion, it completes Ok, but it doesn't also update the Repository folder name which stays with the incorrect case.
it wouldn't let me saying something to the effect of "A job with this name already exists" so I had to change it to an interim name (BIIR-...) then back to the desired name.