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

[feature]: issue-relation support in API #6236

Open
1 task done
tobias-urdin opened this issue Dec 19, 2024 · 2 comments
Open
1 task done

[feature]: issue-relation support in API #6236

tobias-urdin opened this issue Dec 19, 2024 · 2 comments
Assignees

Comments

@tobias-urdin
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Summary

There is no issue-relation API endpoint in the API.

There is such an endpoint for the app on /api/workspaces/{workspace}/projects/{project}/issues/{issue}/issue-relation/ but there is no such endpoint in the API on /api/v1/workspaces/{workspace}/projects/{project}/issues/{issue}/issue-relation/

Why should this be worked on?

If you are migrating issues from another system, or just want to managed relates_to/blocked_by/blocking relationships between issues using the API that is currently not possible and you must do it through the UI or directly in the database.

@tobias-urdin
Copy link
Author

tobias-urdin commented Dec 19, 2024

It would be nice if it also supported overriding with created_by and created_at like the other API endpoints, when migrating from another system that's very useful.

@tobias-urdin
Copy link
Author

To anybody landing here and want a workaround. We abuse the API that is used by the web app on:

POST /api/workspaces/{workspace}/projects/{project_id}/issues/{issue_id}/issue-relation/

By passing the session-id cookie and that working for now, but that's not the official v1 API so this feature is still needed in the official API.

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

No branches or pull requests

3 participants