makeplane / makeplane/plane

[feature]: Link Processes Between Projects Using Tags

Open
#6,852 0 comments 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Mar 31, 2025.

✨feature
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Problem Statement

Currently, Plane.so allows users to create multiple projects, each containing its own processes (workflows). However, there is no way to link a process in one project to another process in a different project.

This becomes an issue when a process in Project A depends on work being done in Project B. For example:

  • Project A has two processes: A1 and A2.
  • Process A2 requires development efforts from Project B.
  • There is no clear way to indicate this dependency or track progress across projects.

Would love to hear feedback from the maintainers on this! Would this align with the vision for Plane.so? 🚀

Why should this be worked on?

Proposed Solution

Introduce a feature that allows users to link processes between projects using tags or explicit relations.

  • Each process can have a "linked processes" section where users can associate it with processes from other projects.
  • Links could be categorized using tags (e.g., "Development Dependency," "Review Required," etc.).
  • Display linked processes in the UI, showing status updates across projects.

Expected Benefits

  • Better cross-project collaboration: Teams can easily track dependencies between projects.
  • Improved workflow visibility: Users can see related work happening across different projects.
  • More efficient project management: Project managers can anticipate delays caused by dependencies.

Potential Implementation

  • Add a new "linked_processes" field in the database, referencing processes from different projects.
  • Extend the UI to allow selecting and displaying linked processes.
  • Implement filtering by tags to differentiate the types of links.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.