Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat]: Pivotal Importer, Save Story History as a Comment #82

Open
semperos opened this issue Oct 16, 2024 · 2 comments
Open

[Feat]: Pivotal Importer, Save Story History as a Comment #82

semperos opened this issue Oct 16, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@semperos
Copy link
Member

semperos commented Oct 16, 2024

The Pivotal Tracker export can optionally include a separate file that provides the history of changes made to the original PT stories.

Even though Shortcut does not provide a means by which to change history in the past for a Story in the present, it could import the history provided in the PT export as a comment on the imported Shortcut stories.

Extend the recipe to include a table of the history pertinent to each imported Story as a comment on the Story, with clear indication that it's a dump of the history and not a real person's comment.

The field's found in the PT history export are as follows:

  • ID
  • Type
  • Message
  • Performed By
  • Occurred At
@semperos semperos added the enhancement New feature or request label Oct 16, 2024
Copy link

Unfortunately, this feature cannot be implemented with the current architecture due to fundamental limitations in Pivotal Tracker's CSV export format:

  1. According to Pivotal's official documentation:

    File attachments (including Google Drive attachments), project history, and story history are not included in the exported file.

  2. The current importer is designed to work exclusively with CSV exports and does not have Pivotal API integration.

Options to consider:
a) Close this issue as "won't fix" due to the CSV export limitation
b) Re-scope the feature to include Pivotal API integration, which would be a significant architectural change:

  • Would require adding Pivotal API authentication
  • Need to fetch story history via API before/during import
  • Would need to modify the import process to handle API rate limits
  • Would increase import time significantly

Recommendation:
Given that this would require significant architectural changes and the importer is currently designed for CSV-only operation, I recommend closing this as "won't fix" and documenting this limitation in the README.md.

@cdemwell
Copy link
Contributor

To clarify, the main CSV export contains no history, but during the export process the Pivotal Tracker user can ask to export history into a separate file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging a pull request may close this issue.

2 participants