-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3
-
Severity 3 - Minor
-
Issue Summary
When we update an existent Compass component without changing the component name, and type, the component information disappears.
Steps to Reproduce
- Go to import a Component
- Click on CSV import;
- Add a CSV without changing the component name, and type, but with modifications to update;
- Check the component information
Expected Results
According to the documentation here:
- If the component name and type in the CSV file matches a component in Compass with the same name and type, any other data you change about that component will be updated.
Actual Results
Even not adding empty rows on the CSV, the information that was already added disspears.
Workaround
The temporary suggestion for now is to add column (lifecycle stage) and column(tier) in cvs file.
[COMPASS-5] When updating a Compass component through CSV, the component information disappears
| Workflow | Original: JAC Bug Workflow v3 [ 4440869 ] | New: JAC Bug Workflow v4 [ 4584639 ] |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | Original: 1 | New: 2 |
| Assignee | Original: Huimin Pang [ 9d911a21ee8c ] |
| Summary | Original: When updating a Compass component trough CSV the component information disappears | New: When updating a Compass component through CSV, the component information disappears |
| Description |
Original:
h3. Issue Summary
When we update an existent Compass component without changing the component name, and type, the component information disappears. h3. Steps to Reproduce # Go to import a Component # Click on CSV import; # Add a CSV without changing the component name, and type, but with modifications to update; # Check the component information h3. Expected Results According to the documentation [here|https://developer.atlassian.com/cloud/compass/components/create-and-update-components-using-a-csv-file/#update-components-using-a-csv-file]: {quote} * If the component name and type in the CSV file matches a component in Compass with the same name and type, any other data you change about that component will be updated. {quote} h3. Actual Results Even not adding empty rows on the CSV, the information that was already added disspears. h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
When we update an existent Compass component without changing the component name, and type, the component information disappears. h3. Steps to Reproduce # Go to import a Component # Click on CSV import; # Add a CSV without changing the component name, and type, but with modifications to update; # Check the component information h3. Expected Results According to the documentation [here|https://developer.atlassian.com/cloud/compass/components/create-and-update-components-using-a-csv-file/#update-components-using-a-csv-file]: {quote} * If the component name and type in the CSV file matches a component in Compass with the same name and type, any other data you change about that component will be updated.{quote} h3. Actual Results Even not adding empty rows on the CSV, the information that was already added disspears. h3. Workaround The temporary suggestion for now is to add column (lifecycle stage) and column(tier) in cvs file. |
| Status | Original: Needs Triage [ 10030 ] | New: In Progress [ 3 ] |
| Support reference count | New: 1 |
| Assignee | Original: Erik Budtke [ c9361b7d4664 ] | New: Huimin Pang [ 9d911a21ee8c ] |
We have attempted this work around, adding lifecycle column and tier column. We have found that when CSV was uploaded this cleared any previous links added to the component on the right hand side pannel (such as links to repositories or documentation). This also cleared any oncall schedules which were previously linked. So unfortuantely this does not work for us.