migrate bug report to gitea #1

New Issue

dominik · 2023-02-04T10:47:16Z

dominik commented

2023-02-04 10:47:16 +00:00

No description provided.

dominik self-assigned this 2023-02-04 10:47:16 +00:00

dominik commented

2023-02-04 11:15:47 +00:00

Users are redirected to phabricator for issue, use API to create issues.

dominik added the

Status

Need More Info

label 2023-02-04 14:22:39 +00:00

dominik commented

2023-02-04 14:36:18 +00:00

Users are redirected to phabricator for issue, use API to create issues.

This does not work for arbitrary users: API does not allow username/password and retrieving a token needs a login, so the issue can be created here directly...

> Users are redirected to phabricator for issue, use API to create issues. This does not work for arbitrary users: API does not allow username/password and retrieving a token needs a login, so the issue can be created here directly...

markusro commented

2023-02-05 13:37:24 +00:00

IMHO there are two ways to tackle this:

The way organizations work in gitea it seems like I have to reevaluate the strategy. This does not work as I thought, i.e.
I can not use a team from another Organization, users are not automatically in the IPKM-public org, etc.

Move the repo to IPKM and assign agvogel team as owner, so that the actual users can create tickets. This is OK for this repo, but intergroup collaboration should be also possible. I have to look how I can do this.
The default for IPKM would be then "public" and IPKM-public is not needed anymore.
This would solve the LDAP mapping of the groups, as that is already setup.
Create a dummy user, make a token. That access token can be used then for that ticket creation. The dummy user must be in the correct team. The user creating the ticket is then basically unknown to gitea, one could put the username in the body of the template though.

IMHO there are two ways to tackle this: The way organizations work in [gitea](https://docs.gitea.io/en-us/permissions/) it seems like I have to reevaluate the strategy. This does not work as I thought, i.e. I can not use a team from another Organization, users are not automatically in the IPKM-public org, etc. 1) Move the repo to IPKM and assign agvogel team as owner, so that the actual users can create tickets. This is OK for this repo, but intergroup collaboration should be also possible. I have to look how I can do this. The default for IPKM would be then "public" and IPKM-public is not needed anymore. This would solve the LDAP mapping of the groups, as that is already setup. 2) Create a dummy user, make a token. That access token can be used then for that ticket creation. The dummy user must be in the correct team. The user creating the ticket is then basically unknown to gitea, one could put the username in the body of the template though.

markusro commented

2023-02-05 14:25:03 +00:00

The damaris-script-library repository is working I think:

https://gitea.pkm.physik.tu-darmstadt.de/IPKM/damaris-script-library/settings/collaboration

The rights look correct:

Owners
administrators
agvogel
can add second team (read only)

The damaris-script-library repository is working I think: https://gitea.pkm.physik.tu-darmstadt.de/IPKM/damaris-script-library/settings/collaboration The rights look correct: - [x] Owners - [x] administrators - [x] agvogel - [x] can add second team (read only)

markusro commented

2023-02-05 14:27:58 +00:00

Shall I move it the IPKM organization?
We would have to fix the links again ...

Shall I move it the IPKM organization? We would have to fix the links again ...

markusro self-assigned this 2023-02-06 19:41:47 +00:00

markusro commented

2023-02-06 19:42:28 +00:00

This is moved to the other org (IPKM).

markusro closed this issue

2023-02-06 19:42:28 +00:00

elisa referenced this issue

2023-07-05 09:54:09 +00:00