You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the latest code available on the main branch of the api-cookbook repo.
Is there an existing issue for this?
I have searched the existing issues.
Current Behavior
If you create a Custom Field in the Shortcut GUI, then attempt to import a Pivotal Tracker the import fails with the following error message. ({Path} replaces real path)
Traceback (most recent call last):
File "/{Path}/api-cookbook/pivotal-import/initialize.py", line 587, in <module>
sys.exit(main(sys.argv))
File "/{Path}/api-cookbook/pivotal-import/initialize.py", line 572, in main
cfg = load_config()
File "/{Path}/api-cookbook/pivotal-import/lib.py", line 448, in load_config
return validate_config(populate_config())
File "/{Path}/api-cookbook/pivotal-import/lib.py", line 344, in populate_config
priority_custom_field_id = default_priority_custom_field_id()
File "/{Path}/api-cookbook/pivotal-import/lib.py", line 289, in default_priority_custom_field_id
if custom_field["canonical_name"] == "priority" and custom_field["enabled"]:
KeyError: 'canonical_name'
make: *** [Makefile:19: initialize] Error 1
Dumping the custom_field variable shows that for user created Custom Field, the "canonical_name" field does not exist.
Expected Behavior
The Pivitol Tracker importer is able to import Pivitol Tracker exports after a Shortcut Custom Field is created.
Minimal Reproducible Example
Manually create a Custom Field in Shortcut
Execute the importer initialization of the Pivotal Tracker importer.
Environment
Operating system: Ubuntu/Windows
Python/JavaScript version: Python 3.10
Further Information
The workaround to continue evaluating the imported that I used was to move the custom_field["enabled"] check before the custom_field["canonical_name"] == "priority" check and disable the custom fields I created in the GUI. Then I was able to execute the import.
The text was updated successfully, but these errors were encountered:
Do I have the most recent api-cookbook code?
main
branch of the api-cookbook repo.Is there an existing issue for this?
Current Behavior
If you create a Custom Field in the Shortcut GUI, then attempt to import a Pivotal Tracker the import fails with the following error message. ({Path} replaces real path)
Dumping the custom_field variable shows that for user created Custom Field, the "canonical_name" field does not exist.
Expected Behavior
The Pivitol Tracker importer is able to import Pivitol Tracker exports after a Shortcut Custom Field is created.
Minimal Reproducible Example
Environment
Further Information
The workaround to continue evaluating the imported that I used was to move the
custom_field["enabled"]
check before thecustom_field["canonical_name"] == "priority"
check and disable the custom fields I created in the GUI. Then I was able to execute the import.The text was updated successfully, but these errors were encountered: