Better management of content staging
The ability to "record" operations and tag them with a name. Also, be able to edit the session and add to it. That way when it's time to promote to production, you can select a group by name to promote.
Chanan Braunstein
shared this idea
3 comments
-
I see. Other problem with this would be the consistency of data, not synchronizing items in the order how they were edited the result may be inconsistent. Anyway, we will see what we can do about it in future and how many votes this gets. I can say for now we won't have enough time to cover that in version 7.
-
Chanan Braunstein
commented
our typical situation is different. In our case, a developer would go into Dev to address a defect or a new feature and make the changes. After some time we would promote the changes to Staging and then to production. The issue we have is sometimes items are addressed but promoted in a different order. Currently it is very hard for us to figure what needs to be moved as part of a release.
Therefore my suggestion is:
1. Every row in the content staging should have a Session Name associated with it (This would be either a name given by the user or something like "Uncategorized").
2. All changes that are not associated with a session would be Uncategorized and will continue to work the same way they do now.
3. A user could also go to the Content Staging UI and click a button - Start New Session. At this point the user will supply a session name.
4. All changes from this point on (till the user click stop session button or logs off) will be tagged with the session name.
5. A drop down on the content staging should be added with a list of all the session names (plus the default uncategorized). This should allow the user to either delete a whole session or sync it.
6. Finally another nice to have would be to continue a previous session. -
Hi, could you please be more specific about how the UI for that should look like? Please note that typical situation is a set of changes from various UIs where the person may or may not realize that he or she does some change that changes some data that is synchronized by staging.
What we plan is filtering of the actions by users and staging profiles.
