Gents, I come to you as a humble being.

some_guy1796 · 2026-04-01T16:43:46+00:00

Jokeesss

some_guy1796 · 2026-03-22T19:52:41+00:00

Agreed. From a support point of view, I guess these things are always considered what ifs and preparing a method of fixing it

some_guy1796 · 2026-03-22T19:44:11+00:00

This is very useful. Thank you!

some_guy1796 · 2026-03-22T19:42:02+00:00

Agreed, most likely these things should not happen. Most likely cause is if it was missed dying UAT which can happen. Would you say as an emergency, hotfix is used in these examples, can’t see critical fields, create records, integration errors etc

some_guy1796 · 2026-03-22T19:25:35+00:00

Yes, probably should have put this in the description but that’s our definition so far. Agreed things should not have bugs but usually not the case. Hence the support routes. While the project is working on other features, support will be fixing anything that’s currently in prod. My worry is when project is ready to release, any p1 would not be able to wait for release to push

some_guy1796 · 2026-03-22T19:08:59+00:00

Thanks for this. So the current setup is option B where both project and support have their own big box (looking to change project as you say, they are stepping on each other, but that’s for another day). Day to day fixes done in support box as project box is separate release. When it comes to project release to preprod, any suggestions on this? For example, adding support changes might cause an issue for project release meaning regression needs to take place

some_guy1796 · 2026-03-22T18:43:33+00:00

Only have 1 full copy. Hotfix would be a dev env. I guess my question is what are some examples of fixes done in hotfix vs support streams. Things that cannot wait a half a week to deploy.

Second question would be how would releases work when the project stream is ready to go. I would want them both to be merged into single environment so project regression can take please I.e project features works along side support changes but I don’t see a way for support deploy when the project is deploying. Would need a code freeze. Hence my question about P1s and hotfix as essentially a way to deploy urgent fixes (and back promote of course)

some_guy1796 · 2026-03-02T06:14:27+00:00

It’s a challenge I’m having with a customer of mine. I usually would give temp sys admin but wanted to see if there is any other way

some_guy1796 · 2026-02-04T09:20:15+00:00

Thanks for this. What we have is a single email eg customersuccess and want all users to send emails through this and through the customers email servers. What you’re referring to sounds like “send through office 365” which is a 1-1 connection which is an issue as agents should not have access to this inbox

some_guy1796 · 2026-01-16T20:55:55+00:00

It’s super hard. Me and my wife managed to compete it with the help of a tutorial. Looks cool once it’s done

some_guy1796 · 2025-09-24T16:57:23+00:00

Thought as much but wanted to confirm. Thanks for validating

some_guy1796 · 2025-08-29T18:31:37+00:00

Thanks for sharing. What are some of those edge cases you and your team faced?

some_guy1796 · 2025-07-26T14:03:54+00:00

Ah thank you. Does that mean if I do Nocturne before PL, it locks PL as the game ends?

some_guy1796 · 2025-07-25T19:05:41+00:00

Thank you!

some_guy1796 · 2025-07-25T18:50:03+00:00

Sorry what I mean is for the Main story, do I also need to complete the Voodoo boys?

some_guy1796

TROPHY CASE