You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We ingest data from many sources and vendors. One of the issues we are currently trying to resolve is how to handle these types of issues. We don't want to create "Bug" tickets, as there is nothing for us to do, i.e. we don't want developers working on these issues.
We also want to be able to differentiate them from internal issues and be able to associate them with the the vendor/source/client, so that when we have discussions with them, we can easily generate a report with all of the open issues.
What we're doing now, is that we created a new issue type called "External Issue". This allows it to be easily filtered from our boards, but allows us to link other tickets, both our service desk, and our development bug tickets to them so we can see how they affect our systems. i.e. does an issue with a 3rd party vendor result in 1 customer issue or 30 customer issues.
How do other's handle this use case? We considered a separate project for all of our external issues, but that seemed overkill. Though the benefit would be that the issues could be shared across multiple projects.