OutSystems DevOps Model Series: 5-Support
We are finally reaching the end of our journey.
Last but not least, we need to talk about support, especially in mission critical scenarios that are already being used by End Users.
In our model we work with multiple teams and projects and in case we need to support the application with multiple maintenance teams as well, how can we keep that organized too?
Who should be involved in each case?
Depending on the type of problem we should send this issue to the right person.
The “Issue Journey” in a high-level overview would be:
However, just this is not enough. We have multiple possible scenarios for bugs in a CD process.
And now that we have all our roles and releases phases, when we have a PRD issue who we should involve?
Well… it depends.
As we said we may have different scenarios for that, and we should handle them accordingly:
- In case it is not a critical issue we should create a backlog item and follow the normal path:
- In case it is a critical issue and we have different versions in PRD and DEV, we should hot fix it in PP and Merge the code with the DEV version if needed:
- In case it is a critical issue and we have the same versions in PRD and DEV, we should hot fix it in PP and backport the fix to DEV:
And that completes our Model!
With it you will be able to work in an organized way with multiple teams and still keep it secure.
I hope this can help you to organize your DevOps Model when using OutSystems.
Previous: 4 — Release Management
OutSystems DevOps Series Articles:
Disclaimer: Most of the material was gotten from OutSystems documents
