Import / Export Issues

petrosilius commented

2023-03-15 22:45:59 +00:00

It would be nice to have the ability to export and import issues as CSV files.

In Gitlab this helps us a lot to process issues externally and import again or copy issues from one project to another.

We used this feature in the past to create a repo with a copy of issues for each of our searchwing.org rescue drones where we need to finish each issue before taking the drones into mission.

It would be nice to have the ability to export and import issues as CSV files. In Gitlab this helps us a lot to process issues externally and import again or copy issues from one project to another. We used this feature in the past to create a repo with a copy of issues for each of our searchwing.org rescue drones where we need to finish each issue before taking the drones into mission.

norwin commented

2023-03-23 00:14:28 +00:00

You can use the tea cli to print issues as csv files:

tea issues -o csv -f index,state,author,title,body -r my/repo

You can use the [`tea` cli](https://gitea.com/gitea/tea) to print issues as csv files: ``` tea issues -o csv -f index,state,author,title,body -r my/repo ```

n0toose added the

enhancement

label 2023-04-20 17:14:04 +00:00

n0toose added the

s/Forgejo

label 2023-04-20 17:34:52 +00:00

gponzo commented

2023-10-17 22:01:56 +00:00

You can use the tea cli to print issues as csv files:
tea issues -o csv -f index,state,author,title,body -r my/repo

I've just tryed but getting thiss result:
2023/10/17 23:59:56 Unknown API Error: 404 Request: '/gponzo/xxx_my_repo_xxx/api/v1/version' with 'GET' method 'map[Authorization:[Basic Z3BvbnpvOjIwQzBkMzIxQjNyZyE=]]' header and 'Not found. ' body

> You can use the [`tea` cli](https://gitea.com/gitea/tea) to print issues as csv files: > > ``` > tea issues -o csv -f index,state,author,title,body -r my/repo > ``` I've just tryed but getting thiss result: `2023/10/17 23:59:56 Unknown API Error: 404 Request: '/gponzo/xxx_my_repo_xxx/api/v1/version' with 'GET' method 'map[Authorization:[Basic Z3BvbnpvOjIwQzBkMzIxQjNyZyE=]]' header and 'Not found. ' body `

fnetX commented

2023-10-17 22:09:03 +00:00

Owner

The API call seems to be nonsense. The version route is at /api/v1/version and has always been IIRC. You might want to ensure rotating your sessions etc, not sure what this Basic Authorization token is about.

gponzo commented

2023-10-17 22:09:57 +00:00

It was my fault, but still not able to complete:
tea-0.9.2-linux-amd64 login add
? URL of Gitea instance: https://codeberg.org
? Name of new Login [codeberg.org]: gponzo
? Do you have an access token? No
? Username: gponzo
? Password: *************
? Set Optional settings: No
Error: token does not have at least one of required scope(s): [read:user]

tea-0.9.2-linux-amd64 login add was required whan issuing the command you suggested.

What am I doing wrong?

It was my fault, but still not able to complete: `tea-0.9.2-linux-amd64 login add` `? URL of Gitea instance: https://codeberg.org` `? Name of new Login [codeberg.org]: gponzo` `? Do you have an access token? No` `? Username: gponzo` `? Password: *************` `? Set Optional settings: No` `Error: token does not have at least one of required scope(s): [read:user]` `tea-0.9.2-linux-amd64 login add` was required whan issuing the command you suggested. What am I doing wrong?

fnetX commented

2023-10-17 22:13:19 +00:00

Owner

Hmm I never used this tool, to be honest. You might get around this by creating an access token with read permissions as described in https://docs.codeberg.org/advanced/access-token/

But I still wonder why this does not work if you answer that you have no token …

Hmm I never used this tool, to be honest. You might get around this by creating an access token with read permissions as described in https://docs.codeberg.org/advanced/access-token/ But I still wonder why this does not work if you answer that you have no token …

gponzo commented

2023-10-17 22:21:43 +00:00

Thank you :)

I've created a token with permissions (R/W) on issues, and given to tea but I receive the very same error:
Error: token does not have at least one of required scope(s): [read:user]

:(

Thank you :) I've created a token with permissions (R/W) on issues, and given to tea but I receive the very same error: `Error: token does not have at least one of required scope(s): [read:user]` :(

fnetX commented

2023-10-17 22:27:20 +00:00

Owner

I think it wants read scope on the user itself. I suppose they want to check your user account details to verify your login or something.

The personal access token thing is a mess in my eyes. Maybe you can have a look if https://codeberg.org/RobWalt/codeberg-cli is an alternative. There's a vivid community around this tool, maybe they can even help you out with the other option.

I think it wants read scope on the user itself. I suppose they want to check your user account details to verify your login or something. The personal access token thing is a mess in my eyes. Maybe you can have a look if https://codeberg.org/RobWalt/codeberg-cli is an alternative. There's a vivid community around this tool, maybe they can even help you out with the other option.

❤️ 1

Import / Export Issues #960