🤔 If we no-go QuickSight, do we sunset the tactical solution? #3152
Labels
data-platform-apps-and-tools
This issue is owned by Data Platform Apps and Tools
enhancement
enhancing an existing feature
stale
Comments
jacobwoffenden
added
enhancement
|
Let's rewrite this to cover the migration plan instead. |
|
This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open. |
|
This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you! |
github-project-automation
bot
moved this from 🎉 Done
to 🚀 In Progress
in Analytical Platform
|
This issue is being marked as stale because it has been open for 60 days with no activity. Remove stale label or comment to keep the issue open. |
|
This issue is being closed because it has been open for a further 7 days with no activity. If this is still a valid issue, please reopen it, Thank you! |
github-project-automation
bot
moved this from 🚀 In Progress
to 🎉 Done
in Analytical Platform
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story
As a Analytical Platform engineer
I want us to come to a decision on the future of QuickSight if we decide to no-go it
So that we don't still end up maintaining QuickSight if its not our tool of choice
Value / Purpose
We (Analytical Platform) provide QuickSight in a tactical offering, as in its not part of core product.
Useful Contacts
No response
User Types
No response
Hypothesis
If we decide to no-go QuickSight
Then sunset QuickSight
Proposal
No response
Additional Information
No response
Definition of Done
The text was updated successfully, but these errors were encountered: