add issues export/import #132

Open
opened 2020-05-04 15:01:30 +00:00 by 6543 · 2 comments
Owner

a function witch can create issues from a csv or yaml file witch was created by tea via tea issues -o yaml

so you can backup and restore issues easely

a function witch can create issues from a csv or yaml file witch was created by tea via `tea issues -o yaml` so you can backup and restore issues easely
6543 changed title from acc `issues import` -b a to add `issues import` 2020-05-04 16:35:47 +00:00
6543 added the
kind
feature
label 2020-07-14 02:32:54 +00:00
Member

We can't cover this use case fully at the moment, as the API (afaik) does not provide a way to set the author of an issue.

Also tea issues ls does not output the issue body, we might need a field-selection mechanism like in tea repos ls for that

We can't cover this use case fully at the moment, as the API (afaik) does not provide a way to set the author of an issue. Also `tea issues ls` does not output the issue body, we might need a field-selection mechanism like in `tea repos ls` for that
6543 changed title from add `issues import` to add `issues export/import` 2020-10-22 13:46:51 +00:00
Author
Owner

@noerw agree, I think we at first infent a export, so tea can be used as backup tool for repos hosted on a gitea instance you are not admin at (gitea.com for example).

and for a import you have to be admin on an instance ... then you can use the sudo header to pretend to be user XY ... so I would add two functions: one with sudo and wone who write into body who original was the author ...

@noerw agree, I think we at first infent a `export`, so tea can be used as backup tool for repos hosted on a gitea instance you are not admin at (gitea.com for example). and for a import you have to be admin on an instance ... then you can use the sudo header to pretend to be user XY ... so I would add two functions: one with sudo and wone who write into body who original was the author ...
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/tea#132
No description provided.