-
Bug
-
Resolution: Fixed
-
Medium
-
10.2.0, 10.3.0, 10.3.1
-
1
-
Severity 3 - Minor
-
Issue Summary
This is reproducible on Data Center: (yes)
Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal. The functionality is broken after upgrade from JSM 5.12.15 to 10.3.2.
Steps to Reproduce
- Step 1 : Create 3 object-types System,role and system-role in Assets
- Step 2 : system-role has attribute pointing to system and role objects.
- Create two custom-fields system and role as shown in attached image. -> System Assets CF.png and Role Assets CF context.png
- Now try to create issue from customer portal and select multiple system.
- Choose corresponding roles.
Expected Results
Customers should be able to create issue from Agent portal.
Actual Results
On the Agent portal issue is created however with same selection customer portal gives error
Please provide a valid value for field 'role'
Workaround
Turn off the feature flag assets.improved.cf.validation
- links to
[JSDSERVER-16003] Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal.
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Fix Version/s | New: 10.5.0 [ 110315 ] | |
| Fix Version/s | New: 10.4.1 [ 110415 ] | |
| Fix Version/s | New: 10.3.4 [ 110310 ] |
| Status | Original: In Progress [ 3 ] | New: Waiting for Release [ 12075 ] |
| Status | Original: Short Term Backlog [ 12074 ] | New: In Progress [ 3 ] |
| Assignee | New: Benjamin Suess [ c8bcca445054 ] |
| Affects Version/s | New: 10.2.0 [ 109023 ] |
| Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: (yes) Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal. The functionality is broken after upgrade from JSM 5.12.15 to 10.3.2. h3. Steps to Reproduce # Step 1 : Create 3 object-types System,role and system-role in Assets # Step 2 : system-role has attribute pointing to system and role objects. # Create two custom-fields *system* and *role* as shown in attached image. -> System Assets CF.png and Role Assets CF context.png # Now try to create issue from customer portal and select multiple system. # Choose corresponding roles. h3. Expected Results Customers should be able to create issue from Agent portal. h3. Actual Results On the Agent portal issue is created however with same selection customer portal gives error {noformat} Please provide a valid value for field 'role' {noformat} h3. Workaround Required, if there is no workaround please state: Turn off the feature flag assets.improved.cf.validation See [https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-server-and-data-center-959286331.html] |
New:
h3. Issue Summary
This is reproducible on Data Center: (yes) Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal. The functionality is broken after upgrade from JSM 5.12.15 to 10.3.2. h3. Steps to Reproduce # Step 1 : Create 3 object-types System,role and system-role in Assets # Step 2 : system-role has attribute pointing to system and role objects. # Create two custom-fields *system* and *role* as shown in attached image. -> System Assets CF.png and Role Assets CF context.png # Now try to create issue from customer portal and select multiple system. # Choose corresponding roles. h3. Expected Results Customers should be able to create issue from Agent portal. h3. Actual Results On the Agent portal issue is created however with same selection customer portal gives error {noformat} Please provide a valid value for field 'role' {noformat} h3. Workaround Turn off the feature flag assets.improved.cf.validation See [https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-server-and-data-center-959286331.html] |
| Description |
Original:
h3. Issue Summary
This is reproducible on Data Center: (yes) Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal. The functionality is broken after upgrade from JSM 5.12.15 to 10.3.2. h3. Steps to Reproduce # Step 1 : Create 3 object-types System,role and system-role in Assets # Step 2 : system-role has attribute pointing to system and role objects. # Create two custom-fields *system* and *role* as shown in attached image. -> System Assets CF.png and Role Assets CF context.png # Now try to create issue from customer portal and select multiple system. # Choose corresponding roles. h3. Expected Results Customers should be able to create issue from Agent portal. h3. Actual Results On the Agent portal issue is created however with same selection customer portal gives error {noformat} Please provide a valid value for field 'role' {noformat} h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
This is reproducible on Data Center: (yes) Choosing more than one value from the many Assets objects chosen in the above field is not possible on the customer portal. The functionality is broken after upgrade from JSM 5.12.15 to 10.3.2. h3. Steps to Reproduce # Step 1 : Create 3 object-types System,role and system-role in Assets # Step 2 : system-role has attribute pointing to system and role objects. # Create two custom-fields *system* and *role* as shown in attached image. -> System Assets CF.png and Role Assets CF context.png # Now try to create issue from customer portal and select multiple system. # Choose corresponding roles. h3. Expected Results Customers should be able to create issue from Agent portal. h3. Actual Results On the Agent portal issue is created however with same selection customer portal gives error {noformat} Please provide a valid value for field 'role' {noformat} h3. Workaround Required, if there is no workaround please state: Turn off the feature flag assets.improved.cf.validation See [https://confluence.atlassian.com/jirakb/how-to-manage-dark-features-in-jira-server-and-data-center-959286331.html] |
| Support reference count | New: 1 |
Hi e06821c0ed96
I have found there is a feature flag to fix this bug, and we will resolve it properly in an upcoming release.
Please see the updated workaround in the description.
Thank you,
Ben - JSM DC