I tried to find an existing topic on this subject but I could not find one that was a good fit, my apologies if I was not thorough enough.
Basically we have a web application that serves multiple clients at multiple corporations (single code base - 'forked' where necessary to accommodate different needs).
This project is a fairly new one as we previously used to make a separate copy of the project per client and maintain it individually. However now that the company is growing, we are adding more staff and also attempting to minimize the code base and relying on configurations to accommodate different needs where possible, as opposed to 'forking'.
The problem I am dealing with now is that our customer relations lady (and it would appear 99% of the rest of the team) really does not understand that changing things on the fly constantly (without due consideration for the impact thereof or the conflicts that may arise) is not the right way about doing things. I mean this completely in the sense of conflicting requirements. We are pretty good at the rest (bugs, testing, scoping etc.)
For instance; Say client X, wants a particular button red but client Y, wants the same button blue (but has possibly requested this change years after X asked for it.) Currently we just make the button blue, until X asks for it to be red again.
This is happening more regularly as our user base is growing. Even worse is when two clients in the same company want conflicting changes.
I am really just a junior developer here, but I see this problem and no one seems to be too perturbed by it, despite my constant nagging. But lately these issues have been falling into MY lap and wasting MY time.
Could anyone please suggest a way that I can try and manage these (even if just for myself).
We currently use OTRS as a client facing ticketing system (for support and requests) and VSO (TFS) for internal tasks and bugs (sometimes created as part of an OTRS request).
I administer both systems, but currently trying to find when last a request came in from a particular client to change a particular button to a particular color in version control history or tickets/emails is just not a very comprehensive nor efficient solution (also the button/color analogy is a really simplified version).
I am just starting to feel like we are headed round in circles and are eventually just going to crash.