Every time I pick up a ticket, it turns out to be a duplicate and another engineer is already working on it or it already is done. So I close the ticket and collect the story points. (Yes, morally correct would be to close it as duplicate with 0 SPs.)

Why not create useless tickets and complete them for even more points?

Beware that if story points are actually used for what they have been invented for (productivity comparison and trend detection), you collecting tons of them in a short time frame sets you up for looking like you tanked in productivity as soon as a ticket actually needs you to do lots of work for closing it.

Feels like these tickets aren't user stories but rather are tasks?

Or could be legit and actually double down on whoever manager/master/superior assigns tickets for failing to keep track of what he assigns who.

@iceb every job Iv'e worked at the employer used story points as man-days and every story is a one big or a set of small tasks

@webketje lol yeah. after experiencing doing scrum more properly and now at a shop that does this.

I hate this tremendously

Same, entered a new job a sprint ago and aint solved any issue yet because they asign me solved ones