Chartbrew v3.0 #177
Replies: 2 comments 1 reply
-
Please, add tagged autocomplete (https://www.npmjs.com/package/react-tag-autocomplete) instead of plain input textbox for filters as well as an option to show added filters on Dashboard Repots page |
Beta Was this translation helpful? Give feedback.
-
Due to the changes in the overall architecture, the current team roles will have to change a bit. This will unfortunately delay the release, but will improve the team management a lot. Currently, most roles (except the owner) are project-level, but this has to change because the connections and datasets are moving to the team-level. The new roles will be: Team-level: Team owner (full project access), Team admin (full project access), Project-only member (specific project access) This will require a migration of current roles. These are the default switches: Owner -> Team owner Please note that only the owner will be moved to the team-level roles. The rest of the admins will have to be added manually if needed. Here's a visual diagram to get a better idea: |
Beta Was this translation helpful? Give feedback.
-
Hey everyone!
V2 was a major shift over v1 and due to the extended usage in both managed and self-hosted versions, we gathered a lot of data that we can use to re-work and improve the product moving forwards. The changes we are going to work on are so big that it warrants a major version change to
v3.0
The main changes that will come to v3 are going to change the way Chartbrew is used. These will affect the way Connections, Datasets, and Projects work.
Currently, each Project comes with its own Connections and each Chart comes with its own Datasets at the project level. This essentially means that each project is completely separate from the other with no way of transferring information. This is great for the flexibility it gives and the amount of resources available (e.g. lots of different connections spread across different projects) but the real usage shows that users are not using it this way - it's more of an inconvenience.
The major v3 change
To answer the inconvenience, we sat down and carefully designed a better experience for new and existing users. The focus will now shift toward Connections and Datasets.
First of all, architecture-wise, the connections, and datasets will both shift to the team level. This means that each project will be able to use the same connections and datasets. If a connection or dataset updates, it will reflect across all projects and charts. Don't want changes to propagate over different projects? You can solve this by creating new connections and datasets the same way it works now in v2.
The data will be migrated automatically so it will not affect existing dashboards
Next, the general flow will change:
A better experience for teams:
This change also takes into account teams with different skills. The connections can be created by people with the credentials to data sources, the datasets can be created with queries by technical&data people, and charts can be created by sales&marketing.
I will update this discussion if there are any plan changes, details, and screenshots to share. Also, feel free to join our discord where you can see more discussions about v3 and Chartbrew in general.
Checklist
Beta Was this translation helpful? Give feedback.
All reactions