Categories
Built in Version control of Catalog objects (GIT, SVN, BitBucket, etc..)
Organization Name
Rogers Communications Canada Inc.
Description
Like any modern application which contains code, it will be great if the OAC catalog incorporates a Version control system like GIT, SVN, etc. At the moment if one author makes a change to a report inadvertently, there is no easy way to see past changes to a report.
I the current OAC version, if an Author changes something and saves a report, the owner of the report does not show who saved the report last. It updates the timestamp but not the owner. This loses traceability and control if there are multiple BI Authors who use the system in a Power User/Citizen Developer/ self-service manner.
Use Case and Business Need
Like any modern application which contains code, it will be great if the OAC catalog incorporates a Version control system like GIT, SVN, etc. At the moment if one author makes a change to a report inadvertently, there is no easy way to see past changes to a report.
I the current OAC version, if an Author changes something and saves a report, the owner of the report does not show who saved the report last. It updates the timestamp but not the owner. This loses traceability and control if there are multiple BI Authors who use the system in a Power User/Citizen Developer/ self-service manner.
More details
Like any modern application which contains code, it will be great if the OAC catalog incorporates a Version control system like GIT, SVN, etc. At the moment if one author makes a change to a report inadvertently, there is no easy way to see past changes to a report.
I the current OAC version, if an Author changes something and saves a report, the owner of the report does not show who saved the report last. It updates the timestamp but not the owner. This loses traceability and control if there are multiple BI Authors who use the system in a Power User/Citizen Developer/ self-service manner.
Original Idea Number: 508d931456
Comments
-
Glad to see this idea is already submitted. Having version control on data sets, data flows, projects, etc., would enable users to revert back to previous versions in the event of accidental mistakes.
0 -
Must needed feature.
0 -
Yes Please, I agree this is needed 100%! Even some basic versioning options would be a start in the right direction. More elaborate versioning tool options that are built-in would be so beneficial for the many users that access and update objects on a regular basis and would greatly assist with troubleshooting.
0 -
Must needed feature
0 -
I voted. Great idea and feature request.
0 -
Many times happened with us. People saved by mistake and revert back is painful.
Version control make sense. Must needed feature.
0 -
Any update since?
0 -
This idea is planned; do we have an expected delivery date?
1 -
This is feature is something our org would really like to leverage. Any update on the timeline?
0 -
Upvoted. Great idea .
0
