JIRA has some specific UX problems in some of the oldest parts of their product which they've been consistently ignoring in favor of multiple menu redesigns. O

JIRA has some specific UX problems in some of the oldest parts of their product which they've been consistently ignoring in favor of multiple menu redesigns. One example off the top of my head... creating filters (custom lists of issues - stored JQL in fact) - why do filters have permissions at all? - why do they always default to private so that I forget every time and share a link which no one can read? - that UI around <Add>ing groups to a filter for permission is a disaster ...that's one example but to me it's symptomatic; PMs at Atlassian jumping on shiny-but-safe things while shying away from the stuff that matters on older features, which may carry legacy.