-
Suggestion
-
Resolution: Unresolved
Issue Summary:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error The value must be a JSON.
Currently, forge custom field is not supported on the bulk edit page and a rendering support for apps on the bulk edit view page is required which means that app will be able to render their own view instead of plain input box that rejects anything that is not a JSON.
Steps to Reproduce
- Create an app that has a customfieldtype in the manifest of type object
- Create a custom field from the customfieldtype
- Associate the field with a project and create a few issues
- Use the project = <project_name> to list the issues and select all the issues
- Then click … on top right corner → Bulk change work items.
- Again, select a few issues and then Click on Next button
- Select Edit issues → Next → try entering some values in forge custom field → Click Next.
Expected Results
When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors.
Actual Results
when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows The value must be a JSON error
Workaround
To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {"test": "abc"} in the custom field, which should be accepted, and allow you to proceed to the next screen.
[ECO-897] Forge Custom Fields on Bulk Edit view
| Description |
Original:
h3. Issue Summary:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{The value must be a JSON}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors. h3. Actual Results when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows {{The value must be a JSON}} error h3. Workaround To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {{\{"test": "abc"}\}} in the custom field, which should be accepted, and allow you to proceed to the next screen. |
New:
h3. Issue Summary:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. Currently, forge custom field is not supported on the bulk edit page and a rendering support for apps on the bulk edit view page is required which means that app will be able to render their own view instead of plain input box that rejects anything that is not a JSON. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors. h3. Actual Results when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows {{The value must be a JSON}} error h3. Workaround To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {{{{}"test": "abc"{}}}} in the custom field, which should be accepted, and allow you to proceed to the next screen. |
| Resolution | Original: Not a bug [ 12 ] | |
| Status | Original: Closed [ 6 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JAC Bug Workflow v3 [ 4528991 ] | New: JAC Suggestion Workflow 3 [ 4531869 ] |
| Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Low [ 4 ] |
| Summary | Original: Forge Custom Field Showing "The value must be a JSON” object on the Bulk Edit screen. | New: Forge Custom Fields on Bulk Edit view |
| Resolution | New: Not a bug [ 12 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Description |
Original:
h3. Issue Summary:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors. h3. Actual Results when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows {{The value must be a JSON}} error h3. Workaround To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {{{"test": "abc"} }}in the custom field, which should be accepted, and allow you to proceed to the next screen. |
New:
h3. Issue Summary:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{The value must be a JSON}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors. h3. Actual Results when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows {{The value must be a JSON}} error h3. Workaround To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {{\{"test": "abc"}\}} in the custom field, which should be accepted, and allow you to proceed to the next screen. |
| Description |
Original:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results h3. Actual Results On the Bulk Edit screen, the object type field shows when attempting to update the Forge Custom Field 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:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results When using the Bulk operations on the Forge Custom Field, users should be able to input value without encountering errors. h3. Actual Results when attempting to update the Forge Custom Field On the Bulk Edit screen, it shows {{The value must be a JSON}} error h3. Workaround To bulk edit object-type custom fields, the input must specifically be a JSON object. For example, you can try entering a value like {{{"test": "abc"} }}in the custom field, which should be accepted, and allow you to proceed to the next screen. |
| Description |
Original:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {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:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results h3. Actual Results On the Bulk Edit screen, the object type field shows when attempting to update the Forge Custom Field 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 |
| Description |
Original:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
As app developers, we would like to have the option to enter data/input as text/strings on the bulk edit page for "object" type custom fields. h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows h3. Steps to Reproduce # Step 1 # Step 2 h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {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:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows the error {{{}The value must be a JSON{}}}. h3. Steps to Reproduce # Create an app that has a customfieldtype in the manifest of type object # Create a custom field from the customfieldtype # Associate the field with a project and create a few issues # Use the project = <project_name> to list the issues and select all the issues # Then click … on top right corner → Bulk change work items. # Again, select a few issues and then Click on *Next* button # Select Edit issues → Next → try entering some values in forge custom field → Click Next. h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {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 |
| Description |
Original:
Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
As app developers, we would like to have the option to enter data/input as text/strings on the bulk edit page for "object" type custom fields. |
New:
To bulk edit, users must manually input values that conform to the expected data types, specifically JSON objects for "object" type fields. This is error-prone, as any mismatch in data types can result in failures.
As app developers, we would like to have the option to enter data/input as text/strings on the bulk edit page for "object" type custom fields. h3. Issue Summary: Currently, when performing bulk edits of object-type custom fields, the system only accepts input in JSON format. When use tries to enter the text, it shows h3. Steps to Reproduce # Step 1 # Step 2 h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {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 |