I’m working with several projects that all use the same shared libraries. When bugs or issues come up in these common libraries, I’m not sure what’s the best approach to handle them in Jira.
Should I create separate tickets for each project that gets affected by the library issue? Or is there some way to set up components that can be used across different projects so I only need one ticket?
Right now I’m duplicating work by making multiple issues for the same library problem. There has to be a better way to manage this. What do other teams usually do in this situation?
Any suggestions on the most efficient workflow for tracking shared dependency issues would be really helpful.
We use Jira’s Epic linking with a centralized setup that works pretty well. I keep one master project just for shared component issues, then create child tickets in each affected product project that link back to the parent. You get visibility into what’s impacted while keeping all the technical discussion in one place. The trick is consistent issue linking and labels so you can spot library problems fast. We also assign library issues to a dedicated team or rotation - having multiple people jump between codebases for the same problem is just inefficient.
We faced a similar challenge in our organization. To streamline our process, we established a ‘Shared Libraries’ project in Jira exclusively for handling issues related to common dependencies. By creating individual components for each library, we could log primary bug tickets there. This method allows us to link related tickets from individual product projects back to the central library issue, ensuring a single source of truth while enabling teams to monitor the impact on their specific projects. Setting up notifications for library maintainers and allowing project teams to subscribe to updates on the main ticket greatly improved our workflow, ultimately eliminating redundant efforts.
we just link issues heavily for this. create the main ticket in the project that owns the library, then add ‘blocks’ or ‘causes’ links from all downstream tickets. it’s messy but you can see the full impact and close everything when it’s fixed.