Actions
Bug #8628
closedProperly restrict job name length
Start date:
12/13/2017
Due date:
07/10/2019
% Done:
100%
Estimated time:
Detected in build:
svn
Platform:
Published in build:
Description
At the moment when a user inputs too long job name, Bridge doesn't provide a nice warning.
Updated by Evgeny Novikov almost 5 years ago
- Detected in build set to svn
- Tracker changed from Feature to Bug
- Priority changed from High to Urgent
- Target version set to 3.0
Moreover, it can corrupt the database. For instance, when I tried to store a job with a long name (after editing existing job files and the job name), Bridge outputted an unknown error. After reducing the job name there was jobs.models.JobHistory.MultipleObjectsReturned .
Updated by Vladimir Gratinskiy almost 5 years ago
- Status changed from New to Feedback
Can't reproduce the bug in bridge-3.0.
Updated by Vladimir Gratinskiy almost 5 years ago
- Due date set to 07/10/2019
- Status changed from Feedback to Resolved
- % Done changed from 0 to 100
There are warnings about big job length, so the bug is not relevant now (bridge-3.0).
Updated by Evgeny Novikov over 3 years ago
- Subject changed from Properly restrict job name lenght to Properly restrict job name length
Actions