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
The importer tool seems great! It has imported hundreds of stories, epics, comments, tags, history and so on, in my initial test.
The problem I have, is that it is bombing out on this exception:
Traceback (most recent call last):
File "/taiga-back/manage.py", line 17, in <module>
execute_from_command_line(sys.argv)
File "/opt/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
utility.execute()
File "/opt/venv/lib/python3.11/site-packages/django/core/management/__init__.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/venv/lib/python3.11/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/venv/lib/python3.11/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/taiga-back/taiga/importers/management/commands/import_from_pivotal.py", line 78, in handle
importer.import_project(project_id, options)
File "/taiga-back/taiga/importers/pivotal/importer.py", line 83, in import_project
self._import_user_stories_data(project_data, project, options)
File "/taiga-back/taiga/importers/pivotal/importer.py", line 400, in _import_user_stories_data
self._import_comments(project_data, us, story, options)
File "/taiga-back/taiga/importers/pivotal/importer.py", line 484, in _import_comments
user=users_bindings.get(comment['person']['id'], User(full_name=comment['person']['name'])),
~~~~~~~^^^^^^^^^^
KeyError: 'person'
There must be a peculiar comment in a specific story but I don't know which. It has imported many other comments so I know it generally is working fine.
The problem is obviously with the data returned from Pivotal. I can't do much about that. But I wondered if a Taiga developer could help me work around this problem in the importer code? Perhaps we can just 'skip' on KeyError rather than fatally error out?
How would I go about editing the code? I am running the command like this:
When I do that, it spins up an instance of taiga-back as a container. I am not building my own image, I'm using the official ones. What's the easiest way for me to perhaps tweak the code? Can I run it directly within the container, perhaps?
Thanks so much for writing this importer! It is looking like it will be a life saver! With Pivotal shutting down, I am sure I won't be the last person looking to migrate to Taiga. :)
Taiga environment
Self-hosted Taiga installed via Docker
The text was updated successfully, but these errors were encountered:
Describe the bug
I am using the Pivotal Tracker importer to import projects from Pivotal Tracker which is being shut down by Broadcom at the end of April 2025.
The importer tool seems great! It has imported hundreds of stories, epics, comments, tags, history and so on, in my initial test.
The problem I have, is that it is bombing out on this exception:
There must be a peculiar comment in a specific story but I don't know which. It has imported many other comments so I know it generally is working fine.
The problem is obviously with the data returned from Pivotal. I can't do much about that. But I wondered if a Taiga developer could help me work around this problem in the importer code? Perhaps we can just 'skip' on KeyError rather than fatally error out?
How would I go about editing the code? I am running the command like this:
When I do that, it spins up an instance of taiga-back as a container. I am not building my own image, I'm using the official ones. What's the easiest way for me to perhaps tweak the code? Can I run it directly within the container, perhaps?
Thanks so much for writing this importer! It is looking like it will be a life saver! With Pivotal shutting down, I am sure I won't be the last person looking to migrate to Taiga. :)
Taiga environment
Self-hosted Taiga installed via Docker
The text was updated successfully, but these errors were encountered: