10 comments

[ 3.1 ms ] story [ 47.6 ms ] thread
Is there anything special about this? Any old project with a public bugtracker is going to have stuff like this. If you browse through Mozilla's (probably one of the oldest around!), you're almost certainly going to find much older bugs.
I think that is most because a company with real paying clients (some very big) with a very expensive product, can't seem able to ship a simple but essential feature as this one. The wow factor here is mind blowing.

Comparing with Mozilla for instance, is a really long shot.

I would counter if the bug has been there for 10 years, and they still have plenty paying customers, it is hardly an "essential feature"
Until you need it. May not be essential, more like, obviously expected kind of feature that breaks the web experience and is highly annoying.
Essential for a few people, probably not the masses! I have used JIRA in team both large and small for around 7 years now and none of us have ever needed this functionality!

Any reason why you cant simply paste a non-clickable link in to what you need?

Or create a plugin to support what you need if it isn't in the core

I'm not clear on why this was posted - just an attempt to get focus on a particularly annoying issue?

Or is it more about highlighting that a 10yo issue exists? (Something not uncommon in long-running projects w/ public trackers.)

She'll be right, mate.

(I'm so happy I don't have to use Jira any longer.)

This isn't even the worst 10 year old issue in my opinion. People have been complaining about the "chattiness" of JIRA for a long time and it's still just as bad. Every change in status for a ticket I get two emails, every comment for a service desk project I get two emails (one with the comment, one with the change in status).

I understand why it happens, but it doesn't seem unfixable.

This can your Admin change.
This seems like some weird marketing attempt from Atlassian?