Is there a way to "exempt" a story from showing up in the burndown? We are using a "scrumban" approach for our production support teams and so we do occasionally have to bring in unplanned work items that may span multiple iterations.
I'm not sure that there's a way to handle this use case as most of those calculations are handled automatically on the backend
David is correct, the calculations run on the back-end. The only way to 'exclude' a story from the burn down would be if you had the Plan Estimate field set to '0'.
Yet, perhaps for curiosity more than anything else, why would you need to exclude/exempt a story from the burndown?
As long as this story is actually worked on then it should be estimated and burndown against the execution. Why should it not?