As a medical student, I found the medical education learning management systems to be an invaluable tool in my education. The user-friendly interface made it easy to navigate through the vast amount of information available, and the interactive features allowed for a more engaging learning experience. The ability to track my progress and receive feedback from instructors was also incredibly helpful in ensuring my success. Overall, I highly recommend these systems to any medical student looking to enhance their education on https://www.reviewsed.com/medical-education-learning-management-systems/.

Haha, 7 years for this totally basic feature, and nothing. Now that Bitbucket has dropped mercurial support (without giving the thousands of developers ANY tool to assist the migration, thank you so much), I'm moving our whole organization to competition. I feel so incredibly relieved already, leaving this whole "Dear customer, I don't give a sh*t about what you need, I know better" attitude behind forever.

Jenifer,

I do not think that this would require a research panel. Much like Jira labels we want to have free form labels to mark and organize our work.

Jennifer, I wish I could use: -1: in your comment like in Github, but I would have to open a new issue because Bitbucket doesn't support it.

LOL

Hi all,

Thank you so much for your votes and comments on this issue. We’d love to learn more from you! Help us improve your experience by joining the Bitbucket Cloud Research Panel and participating in our research studies. Sign up here: https://forms.gle/XzrpgqrusuUVvAe37

— Bitbucket Cloud Design Team

Stiiiiiiiiilll waiting

Still waiting

A basic enhancement to Bitbucket issue labels would be "size". Bitbucket issues have type and priority but size is missing. Yes, you could use other tools but it is so nice to use just repository issues in some cases. Not every development team, project, and repository needs management tools. In GitHub, we define custom issue labels using T-shirt sizes XS, S, M, L, XL, with appropriate descriptions. Using uppercase avoids most confusion such as with "medium" priority and M size. Without a simple label for size in Bitbucket it is harder to do basic issue triage.

I think for them to add labels would make Issues too much of a competitor to Jira. They want to keep Issues lean and simple, and have Jira be the upgrade path.