Connect Wiki Pages to Work Items
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem
The GitLab Wiki serves as a valuable place for teams to document, collaborate, and continually enhance information as part of their knowledge management process. However, within the GitLab ecosystem, the Wiki operates in isolation from other core planning components in the Enterprise Agile Planning workflow, specifically Issues and Epics. This lack of integration results in silos between the knowledge essential for project execution and the practical implementation of the project itself. These isolated knowledge silos can contribute to the development of a suboptimal knowledge management culture.
Solution
To address this challenge, a solution involves establishing connections between Wiki Pages and Issue and Epic object types. Currently, Issue and Epic object types can be interlinked, allowing users to create hierarchies and organize structures within their projects. The proposed improvement aims to extend this connectivity to Wiki Pages, enabling users to draft, collaborate, and refine knowledge on a project directly within a Wiki page. By establishing links between these Wiki Pages and associated Issues and Epics, users gain the ability to seamlessly integrate the knowledge they have developed with the projects they are actively working on. This enhancement facilitates a more cohesive approach to project management, ensuring that essential information is readily accessible and directly aligned with the tasks at hand.
This relates to JTBD five which we've identified for Wiki category after multiple research studies.
Proposal
We can show a "Linked Wiki pages" section near other linked section under an issue/epic description.
Competitor Solutions to Problem
Using Confluence and Jira Together
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.