Re-posting this as a question since I'm not sure if it's a question or more of a discussion point. Any help with this is appreciated.
We use JIRA bug tracking for a software system that's owned by another software company. We perform configuration and customization enhancements, but base functionality of the software is owned by the software company. Sometimes our end users report bugs for which neither we nor the software company have a solution. In these cases, we'll sometimes work on the bugs for a little while intermittently during our sprint work (which isn't ideal, but it happens) or even assign the bugs to the sprint during which we're working on them, with the hopes that we'll be able to find a solution to the issue and add the solution into the next release. It ends up messing with sprint scope, because we don't know if we'll be able to find a solution in the given time-frame and sometimes have to move the bug out of the sprint. These are the kinds of issues where people often randomly find a solution while working on something else and discover there was an issue with a piece of code or something similar.
Do other software developers have this issue? If so, how do you track the work you do on figuring out these seemingly unsolvable issues? Do you track the work within an existing sprint and continue moving the issue to the next sprint if you don't solve it? Or do you let it sit in the backlog and keep revisiting it until someone miraculously finds a solution?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events