Re:The JIRA's 10 years old feature request: support RFC 2396
by gcp on Tuesday February 21, 2017 @12:00PM
(#13697092)
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.
Re:The JIRA's 10 years old feature request: support RFC 2396
by jdright on Tuesday February 21, 2017 @12:07PM
(#13697169)
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.
Re:The JIRA's 10 years old feature request: support RFC 2396
by voycey on Tuesday February 21, 2017 @09:13PM
(#13702306)
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
Re:The JIRA's 10 years old feature request: support RFC 2396
by thomaskcr on Tuesday February 21, 2017 @01:34PM
(#13698088)
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.
Comparing with Mozilla for instance, is a really long shot.
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 so happy I don't have to use Jira any longer.)
I understand why it happens, but it doesn't seem unfixable.
Or is it more about highlighting that a 10yo issue exists? (Something not uncommon in long-running projects w/ public trackers.)