Require unique job names
A long ago we found that in general using job names to reflect all job settings is an awful practice. That's why in Klever in the production mode jobs come with all settings and specifications. Nevertheless, using job names to reflect the most important distinguishing characteristics of corresponding jobs seem to be a valid and useful practice. Moreover, this assumes that all jobs should have unique names. Otherwise, somebody does useless work launching undistinguishable jobs.
I forgot that this feature is required for automated starting job solutions when one knows job names but doesn't know artificial job identifiers.
Updated by Evgeny Novikov over 2 years ago
- % Done changed from 100 to 0
- Status changed from Resolved to Open
Vladimir Gratinskiy wrote:
Implemeted in branch "manage-extension". But now job names are not saved in versions.
Perhaps, this is the reason why after migration I don't see job names (titles) when editing or copying jobs. Moreover, I have to enter each time when performing these operations. This seems strange. Besides, I suggest that all previously specified job names/titles are silently removed that also doesn't match the job history idea. Why did you miss job names in job versions?
Updated by Vladimir Gratinskiy over 2 years ago
The bug with editing job names was fixed. I miss job names in versions because of, for example, uploading jobs. When you populated jobs (before unique jobs patch) second time, you had some jobs with the same names. Then you rename populated jobs, and then names become unique. But if you try to upload one of these jobs, you get an error as the algorithm of uploading is creating job with first version and then applying other versions one by one. And on 1st step names are not unique. To fix all such problems I need to reqrite a lot of functions from zero.