Issue Details (XML | Word | Printable)

Key: BAM-220
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: Ben Kuo
Reporter: Riaz Khanmohamed
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Optional field appears to be mandatory on update (cvs password)

Created: 14/Sep/06 11:29 AM   Updated: 05/Oct/06 06:19 PM
Component/s: Administration (Projects)
Affects Version/s: 0.3
Fix Version/s: 0.4

Time Tracking:
Original Estimate: 1 hour
Original Estimate - 1 hour
Remaining Estimate: 1 hour
Remaining Estimate - 1 hour
Time Spent: Not Specified
Remaining Estimate - 1 hour

Participants: Ben Kuo and Riaz Khanmohamed
Since last comment: 2 years, 16 weeks, 5 days ago
Number of comments: 3
Internal Priority: 1. Highest
Labels:


 Description  « Hide
cvs password is optional. it says so. if you leave it blank on creating the project it doesn't mind. However, if you go back to it later and edit the repository data (updateBuildRepository.action) and then try to save, it says 'repository.cvs.password.required'... but it's optional....

Think there's a check there that doesn't need to be



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Riaz Khanmohamed added a comment - 14/Sep/06 11:30 AM
and in any case, repository.cvs.password.required is not really a usable error message. Might be worth checking if others are throwing unusable errors as well

Riaz Khanmohamed added a comment - 14/Sep/06 11:39 AM
Sorry - can't edit/delete comments. For clarity, this is fine on the normal wizard, so if you edit from the main page using the 'Edit Build' link it's fine. However, if you use the new Build Configuration option on the left then edit the individual source repository details it throws the error.

Ben Kuo added a comment - 15/Sep/06 02:08 AM
The validation has been removed.
However there is still some dodginess surrounding the configuration screen for which I've created a new issue (BAM-224) for.

Thanks for reporting!

Ben