Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

I imported a csv with 131 rows. The issues field had spaces in them, e.g. "Engagement, Plugin, slam"

github-csv-tools ran as expected listing "Imported issue:" for each row present.
Output ended with Created 131 issues, and had 0 failures.

However, 0 issues were present in the Github Issues for that repo.

I edited the file to remove all spaces between items and to remove any empty items e.g. ,,.
Re-ran import in verbose mode.
github-csv-tools ran as expected listing "Imported issue:" for each row present.
Created 131 issues, and had 0 failures.

However, there are only 110 items in the Issue. Some issues silent failed and I don't know why.

You must be logged in to vote

Replies: 2 comments · 1 reply

Comment options

Please provide a replication case.

You must be logged in to vote
0 replies
Comment options

I also faced this issue, and was disappointed that the issue was closed, as I felt the question outlined the problem well.

Here is an example csv of the first problem:

"title","labels","body"
"SAM-104 Document current technical state of project","jira-import,jira-import-230123,task,","Body content"

Notice how there is an empty label, a trailing comma.

Here is an example csv of the second problem:

"title","labels","body"
"SAM-56 Build athena image in balenaCloud builder","jira-import,jira-import-230123,task,Setup CI/CD, Deployment, and Automated testing","Body content"

Notice how there are spaces after the commas preceding some of the labels.

Label syntax issues aside, I think the most obvious issue is that github-csv-tools is silently failing and telling the user that it successfully imported an issue when it in fact did no such thing. At the very least, I would expect better error reporting so I am aware that the import failed (ideally, it could detect these syntax issues before it even starts the import and fail early).

You must be logged in to vote
1 reply
@gavinr
Comment options

Thanks for the clarification. I would accept a PR that fixes the "Spaces before labels" issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
3 participants
Converted from issue

This discussion was converted from issue #89 on October 12, 2022 12:49.

Morty Proxy This is a proxified and sanitized view of the page, visit original site.