Admittedly, this is an issue with organization and can be solved with thorough cleanups, but I suspect that may disrupt the usual flow of non-PM people more. I am thinking of using a separate tool like craft.io or productboard.com to highlight strategies, roadmaps, cross-team initiatives, discoveries, etc. With a possible link to JIRA somehow. Has anyone ever tried this? Source: about 2 years ago

Recently my friend at Productboard noticed an interesting bug in one of our services. For some reason our code responsible for calculating how many days our customers' features spend in certain states (Idea, Discovery, Delivery, etc) in some cases would give us wrong results. - Source: dev.to / about 2 years ago

ProductboardProductboard helps us capture user feedback from email, Slack, Zendesk, our public-facing product portal etc. And see what users need the most. We also use it for prioritizing product objectives, release planning, roadmapping…. Source: almost 3 years ago

I use ProductBoard. It's fairly expensive but pretty great. I gather requirements into PB and use the inbuilt editor to flesh them out. When a story is ready I push a button and it ends up in Trello (but you can add your own integrations; there's one for github for example). The integrations aren't perfect but I love it. Used it in my last job and brought it in at my current job. https://productboard.com. - Source: Hacker News / about 3 years ago

I'm thinking of using some bug bounty type of services to speed up bugfixes and adding new features, anyone has experience with it? I mean services like https://www.bountysource.com/ , https://gitpay.me/ or https://issuehunt.io/. Source: almost 3 years ago

I don't think we have a good model for monetary rewards for maintenance. If Haskell.org was providing support contracts covering a wide range of libraries, I would guess a lot of companies would use the option. However, signing a support contract with a maintainer of every dependency I have is infeasible. Things like Gitpay (bounties for PRs) have been tried time and again, and they never take off. Source: over 3 years ago

Donate to the project, start a company employing devs, buy support from Canonical or RedHat or SuSE, pay for issues to be fixed through GitPay or BountySource. Source: over 3 years ago