It's nice to have options for each bug, but unless you're a big Jira fan, it is not very usable.

I suggest showing the titles on the buttons as soon as they are downloaded, otherwise show the bug IDs (e.g. if the player launches it offline). Once names are downloaded bug IDs would move to tooltips.

Alternatively, some kind of combination of the two, like
Bug name - Bug ID in the button and

Bug name
Bug ID

in the tooltip.

That would maximize the screen real-estate usage if it fits, otherwise allow users to see the full title in the tooltip.

Well, there isn't really much consistency in the naming scheme but it does look more helpful even in the smaller GUI scale.

How much would it fit if the ID came after the name?

In my opinion, this would make the GUI look very messy, it doesn't really speed things up either because all you have to do is hover over to see exactly what it is.

At any sane GUI scale, none of the names fit in like this, because Mojira titles aren't designed to be small!

In my opinion, this would make the GUI look very messy, it doesn't really speed things up either because all you have to do is hover over to see exactly what it is.

At any sane GUI scale, none of the names fit in like this, because Mojira titles aren't designed to be small!

In my opinion, I think this is the best design because if you think this out from a user perspective, they would want to know the Bug ID then what the bug fixes. If they can't see it, they can hover over the bug and see the tooltip to see the full bug description.

I now remembered one thing YACL has - search. So even if bug numbers are preferred, including the title after them would make them searchable and then it wouldn't matter how much of the title is seen as people use keywords anyway.

Therefore, I agree with Imzxhir now.

Honestly, since @mojira titles are supposed to give as much information as possible but in one line, I don't really think this is a good move to display it in the config option - but I believe potentially in a tooltip would be the best option. Ideally, the tooltip with be configurable too.

I wouldn't agree, you can read the first couple of words, then you need to hover anyway to see what it does. Maybe post in #devlog in FO and see what other people think.

I now remembered one thing YACL has - search. So even if bug numbers are preferred, including the title after them would make them searchable and then it wouldn't matter how much of the title is seen as people use keywords anyway.
Therefore, I agree with Imzxhir now.

I could make tooltips be searchable.

Is there a way you can make the title of the bug or the actual bug searchable (not Bug ID)? This is similar to your idea of searchable tooltips

Bug ID should definitely be searchable as well. Imagine the cache use if the bug's contents were cached though... no thanks.

I now remembered one thing YACL has - search. So even if bug numbers are preferred, including the title after them would make them searchable and then it wouldn't matter how much of the title is seen as people use keywords anyway.
Therefore, I agree with Imzxhir now.

I could make tooltips be searchable.

Is there a way you can make the title of the bug or the actual bug searchable (not Bug ID)? This is similar to your idea of searchable tooltips

Honestly, since @mojira titles are supposed to give as much information as possible but in one line, I don't really think this is a good move to display it in the config option - but I believe potentially in a tooltip would be the best option. Ideally, the tooltip with be configurable too.

I'm not quite sure what you mean? Tooltips already exist.

I now remembered one thing YACL has - search. So even if bug numbers are preferred, including the title after them would make them searchable and then it wouldn't matter how much of the title is seen as people use keywords anyway.

Therefore, I agree with Imzxhir now.

I could make tooltips be searchable.

Bug descriptions have been searchable for quite a while now. I think this is a great solution.