@nixCraft Hard to be passionate with JIRA:

• when the implementation you use host more 10000 projects and is incredibly slow
• when admin categorize 3 possible workflows in the running instance and doesn't let you choose which one is the best for your application, neither let you customize the workflow/UI to let you have something matching your needs...
• when you loose 10 years of history on the last JIRA migration because admin considered that closed JIRA are useless and consume too much resources on the instance (it was ~5000 JIRA, ~5GiB once exported...)

It's like Service-Now: maybe they're good softwares, but shitty implementation/settings/UI let you consider that the entire tool is shitty