3 ms·
Jira-1369 was closed four years ago.
by jedberg 3y ago
Jira-1369 was closed four years ago.
- j45 3y agoAs one of jira’s bigger brain farts, it seems it’s was recreated and continued in a new ticket. Open: https://jira.atlassian.com/browse/JRACLOUD-1369 https://jira.atlassian.com/browse/JRACLOUD-1369 Closed: https://jira.atlassian.com/browse/JRA-1369 https://jira.atlassian.com/browse/JRA-1369 The original JRA-1369 was opened in 2003. Addressed a little in 2019, but not the digests to solve it all. Odd since plug-ins have to. closing this is one way to improve optics I guess. Ps, I don’t hate Jira. Wasn’t a huge fan and it took a few years to see the light of what it does that so few platforms do when it comes to being able to absorb complexity as it evolves. Managing evolving complexity is a real thing, and the pain can be reduced by having more in one tool vs not. It’s a tough space, and I think Aha.Io is one tool suited to win their prize and grow into Jira’s space. Their worst sin remains how many people are subjected to an out of the box install compared to one that is setup to your processes. Tweaking it makes such a difference.
- jedberg 3y agoAh you're right, it was just reopened. > Their worst sin remains how many people are subjected to an out of the box install compared to one that is setup to your processes. Tweaking it makes such a difference. This is true, I hated out of the box Jira, and I tolerated it after I tweaked it for our org. Honestly, it probably shouldn't even work out of the box. It should just start with a single ticket that describes how to configure it, that you can't close until you configure some ways to close tickets.
- j45 3y agoTotally agree. I was on the out of the box side for too long. It is a little too complicated to setup in the beginning but it has more first principles to learn before combining maybe due to the complexity it can handle.