Details
-
Type:
New Feature
-
Status: In Review
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.11.0
-
Fix Version/s: 5.13.0-b1
-
Component/s: Staff Interface
-
Labels:None
Description
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
Export
1. Under Packages > Configurable Options, add an "Export" option before "Delete".
2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file.
3. Additionally, add an export option for individual Configurable Options, "Export" prior to "Delete". This will allow exporting individual options rather than an entire group if desired.
Import
1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned.
2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group.
3. If it passes validation, create all the options and assign them to this Option Group.
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Paul Phillips
made changes -
| Rank | Ranked lower |
Paul Phillips
made changes -
| Description |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
# Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. # Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
h2. It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
Paul Phillips
made changes -
| Description |
h2. It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
Paul Phillips
made changes -
| Description |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. 3. Additionally, add an export option h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
Paul Phillips
made changes -
| Description |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. 3. Additionally, add an export option h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
It can be a real pain to create lots of config options, and then re-create them with different pricing in a new group if you have different prices for the options on different packages. Adding an export/import option would also make sharing these export files possible so they could be included in module documentation, or with a module, etc.
h2. Export 1. Under Packages > Configurable Options, add an "Export" option before "Delete". 2. Clicking Export will generate a JSON file containing only the options in the group. Include all the details for every option, and include any Option Logic in the generated JSON file. 3. Additionally, add an export option for individual Configurable Options, "Export" prior to "Delete". This will allow exporting individual options rather than an entire group if desired. h2. Import 1. When editing a Config Option Group, add an Import option with file selector. Ideally imports will be done on new groups with no options assigned. 2. Upload the JSON file and do some validation. We want to make sure the JSON data is valid, passes any rules, AND that none of the options in the export file already exist in this group. 3. If it passes validation, create all the options and assign them to this Option Group. |
| Story Points | 5 |
| Sprint | 5.13.0 Sprint 2 [ 217 ] |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 4 hours, 26 minutes [ 15960 ] | |
| Worklog Id | 17792 [ 17792 ] |
| Time Spent | 4 hours, 26 minutes [ 15960 ] | 1 day, 4 hours, 26 minutes [ 44760 ] |
| Worklog Id | 17793 [ 17793 ] |
| Time Spent | 1 day, 4 hours, 26 minutes [ 44760 ] | 2 days, 30 minutes [ 59400 ] |
| Worklog Id | 17804 [ 17804 ] |
| Time Spent | 2 days, 30 minutes [ 59400 ] | 3 days, 27 minutes [ 88020 ] |
| Worklog Id | 17805 [ 17805 ] |
| Time Spent | 3 days, 27 minutes [ 88020 ] | 3 days, 6 hours, 58 minutes [ 111480 ] |
| Worklog Id | 17806 [ 17806 ] |
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
