cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

When Product Bugs are deferred / cannot be fixed.

When Product Bugs are deferred / cannot be fixed.

 We'd like to give you a quick glimpse into what happens behind the scenes of a bug triage and fix journey, so you have a better understanding of why Khoros can't always provide solutions on every issue reported.

We do everything we can for a quick turnaround on bugs, but it's not always possible for a variety of reasons. Bugs are triaged and then identified for possible fixes, based on the complexity of the issue, how widespread the problem is, and other issues already reported in the backlog. This is in addition to any fixes and new features the team is checking into a pending release, unannounced features they have already committed to, as well as the overall QA that must be performed across the board.

Taking all factors into account, sometimes it may take time to resolve a reported issue and some bugs may be deferred.  Our teams are committed to continuously improving our solution and prioritize based on product roadmap.

However, if our team has misunderstood the impact this issue has on you and your users, could you help provide some additional input for me to provide our product team with more insight? While we cannot guarantee it will be reconsidered, we do want to make sure we've captured the severity and impact it has on your team.

 

Status: Won't fix/deferred:-

 Our product and development teams cannot provide any concrete or estimated time frame for when this issue will be prioritized in the product roadmap. This bug has been deferred.  When this particular feature comes up again for review, they will gather all related bugs together and review them for inclusion in the improvements at that time.

Given the current state of the issue, we want to be respectful of your time and patience and set the expectation that the issue will not be addressed anytime soon and feel it would be best to close this case out if the bug is in status.

 

 

 

Tags (1)
Version history
Revision #:
2 of 2
Last update:
‎05-18-2020 06:36 AM
Updated by:
 

When Product Bugs are deferred / cannot be fixed.

 We'd like to give you a quick glimpse into what happens behind the scenes of a bug triage and fix journey, so you have a better understanding of why Khoros can't always provide solutions on every issue reported.

We do everything we can for a quick turnaround on bugs, but it's not always possible for a variety of reasons. Bugs are triaged and then identified for possible fixes, based on the complexity of the issue, how widespread the problem is, and other issues already reported in the backlog. This is in addition to any fixes and new features the team is checking into a pending release, unannounced features they have already committed to, as well as the overall QA that must be performed across the board.

Taking all factors into account, sometimes it may take time to resolve a reported issue and some bugs may be deferred.  Our teams are committed to continuously improving our solution and prioritize based on product roadmap.

However, if our team has misunderstood the impact this issue has on you and your users, could you help provide some additional input for me to provide our product team with more insight? While we cannot guarantee it will be reconsidered, we do want to make sure we've captured the severity and impact it has on your team.

 

Status: Won't fix/deferred:-

 Our product and development teams cannot provide any concrete or estimated time frame for when this issue will be prioritized in the product roadmap. This bug has been deferred.  When this particular feature comes up again for review, they will gather all related bugs together and review them for inclusion in the improvements at that time.

Given the current state of the issue, we want to be respectful of your time and patience and set the expectation that the issue will not be addressed anytime soon and feel it would be best to close this case out if the bug is in status.

 

 

 

Tags (1)

When Product Bugs are deferred / cannot be fixed.

 We'd like to give you a quick glimpse into what happens behind the scenes of a bug triage and fix journey, so you have a better understanding of why Khoros can't always provide solutions on every issue reported.

We do everything we can for a quick turnaround on bugs, but it's not always possible for a variety of reasons. Bugs are triaged and then identified for possible fixes, based on the complexity of the issue, how widespread the problem is, and other issues already reported in the backlog. This is in addition to any fixes and new features the team is checking into a pending release, unannounced features they have already committed to, as well as the overall QA that must be performed across the board.

Taking all factors into account, sometimes it may take time to resolve a reported issue and some bugs may be deferred.  Our teams are committed to continuously improving our solution and prioritize based on product roadmap.

However, if our team has misunderstood the impact this issue has on you and your users, could you help provide some additional input for me to provide our product team with more insight? While we cannot guarantee it will be reconsidered, we do want to make sure we've captured the severity and impact it has on your team.

 

Status: Won't fix/deferred:-

 Our product and development teams cannot provide any concrete or estimated time frame for when this issue will be prioritized in the product roadmap. This bug has been deferred.  When this particular feature comes up again for review, they will gather all related bugs together and review them for inclusion in the improvements at that time.

Given the current state of the issue, we want to be respectful of your time and patience and set the expectation that the issue will not be addressed anytime soon and feel it would be best to close this case out if the bug is in status.

 

 

 

Tags (1)
Contributors