Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.6.0-b1
-
Fix Version/s: 4.6.0-b2
-
Component/s: Client Interface, Staff Interface
-
Labels:None
Description
A custom client field that is not required and not visible to clients, prevents the client from registering an account with the error "[Option Name] is set to an invalid value".
I'm not sure if there is a reason for this, but it seems like a bug. A side affect would be that if the admin modifies the account, some value will have to be saved. However, in the case when an admin wants to select a dropdown option for a client for internal purposes, it shouldn't prevent the client from registering.
Issue Links
- Testing discovered
-
CORE-3378
Custom client field warning message is inaccurate
-
- Open
-
Activity
Paul Phillips
created issue -
Tyson Phillips (Inactive)
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Tyson Phillips (Inactive)
made changes -
| Sprint | 4.6.0 beta Sprint 1 [ 86 ] |
Tyson Phillips (Inactive)
made changes -
| Rank | Ranked lower |
Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour, 3 minutes [ 3780 ] | |
| Worklog Id | 12295 [ 12295 ] |
Automated transition triggered when Jonathan Reissmueller created pull request #680 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Time Spent | 1 hour, 3 minutes [ 3780 ] | 1 hour, 59 minutes [ 7140 ] |
| Worklog Id | 12306 [ 12306 ] |
| Time Spent | 1 hour, 59 minutes [ 7140 ] | 2 hours, 18 minutes [ 8280 ] |
| Worklog Id | 12321 [ 12321 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #680 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
