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

Preserve "Issue Key" when importing from external tool and exporting again #323

Closed
xeronimus opened this issue Jan 2, 2023 Discussed in #320 · 2 comments
Closed

Preserve "Issue Key" when importing from external tool and exporting again #323

xeronimus opened this issue Jan 2, 2023 Discussed in #320 · 2 comments

Comments

@xeronimus
Copy link
Contributor

Discussed in #320

  1. Extend the schema with a new property "key" ("story-key" / "issue-key" ), this should be a optional property (not mandatory)
  2. Store this property when importing from csv (still prepend imported issue-key to title)
  3. On export (json), include this new property in the export
xeronimus added a commit that referenced this issue Jan 2, 2023
…json export

- extended room schema
- make sure storyAdded event contains new property
- make sure new property is stored to room on storyAdded
- make sure to include new property in export
xeronimus added a commit that referenced this issue Jan 2, 2023
@cdwillie76
Copy link
Contributor

I tested this branch and confirmed that the key was export for csv items that had it during import.

@cdwillie76
Copy link
Contributor

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants