So last week there was a meeting at my workplace. In short the meeting concluded that me and 3 other devs gonna develop a fairly complicated system. I was happy to test my skills after 2 years of bug fixing in already working systems. Yesterday I found out that other people gonna do it with an other technology and I'm stuck with bug fixing for God knows how long...
Ps: feedback shows I'm not a bad dev.

I feel your pain, however, can I suggest you treat the situation with a "glass half full" mentality rather than "glass half empty". Code refactoring and dealing with legacy code is a good skill to have so try to focus on that. Situations like this suck, but whenever life throws lemons, make lemonade! Hope you get an exciting project soon.

I consider bug fixing as challenging hahah
I guess that says a lot regarding my skill :P

I really enjoy bug fixing, but my team is eager to get me on feature implementation because of some unspoken stigma against bug fixing. In my mind, there will always be bugs to fix that directly affect the user, and it makes me feel good to fix a problem that's been annoying actual people.

While it's progress, no user has asked us to rebuild a working page to make it prettier, but a hundred people are asking us to fix things that should already work.

I'm sorry they've kept you on them for so long. I hope they let you venture out into new things.

Also-- do you have one-on-ones with your direct manager? If so, don't be afraid to bring this up. It shows you want to progress, which never looks bad.

@g-m-f it is hard to find a job as a dev where I live, I would need to move to an other city.

@BrokeTheInteger I talked to my direct superior about this, but it did not make a difference right now, maybe later on it will have some effect. Thank you for your advice :)

@ymas Thanks for this motivating advice I will try to keep it in mind. :)