3 ms·

jira-1369 is a 20 year old bug of email notifications not being put into a digest and instead flooding users. I for one feel like I grew up those people and we

• xp84 3y ago
  Even though I’ve come to like Jira there are a few of these 15-20 year bugs that are just frustrating beyond belief. And a Jira PM will duck in there every 8 years or so to say they’re not considering it and then run away. Mine is how it’ll let you create infinite case variations of Labels, even though Labels are case-insensitive when querying, but it means the accidental variations people will make crap up the autocomplete forever. Or the fact that Components or Versions can’t exist across multiple Projects. Thankfully we did basically automate Version management using their Automations to basically fake it. Thankfully Versions in JQL are searched by string instead of being instantly converted to ID like Sprints are.
  • j45 3y ago
    Part of me feels like writing a new interface of what I need to Jira using their API to get things how they're needed while maintaining some meaningful compatibility. Then I remind myself I'm not the only person to ever think that. What amazes me is the number of times JIRA has landed at a clients while we are working with them (from us introducing them). It is excitedly rolled out to hundreds of employees on a project eam after they see what it can do with modifications for their workflow. Every single deployment has eventually been shut down because Confluence can't digest updates every 5-10 minutes, nor can Jira. A plugin isn't realistic in some cases, so some other ways was found around it.