Joshua Caron

Hi Alex,

I ran a query through Jira before opening this ticket and found several tickets for the same issue that were opened and closed. When I work using Jira we would link all related/duplicate tickets. If there was an active ticket it wasn’t linked at the time that I opened this ticket. Just a suggestion and probably difficult given that this is open sourced but if a bug is confirmed linking it to previous cases might result in less duplication in the future. Then again when I work in QA our customers don’t raise tickets using the same system we do so there’s no overlap like there is here.

I use this ticket system at work and we usually linked related issues. I'm not able to link issues (assuming only Mojang staff are capable of doing this). Anyways, this is similar to MC-148955 and I suspect it is duplicate. However, that ticket is marked as resolved which is why I have opened this ticket.

Thanks