It's just sad to see how this went down!
I just tried and also wasn't able to "reproduce" the bug I had initially reported.
In other words: this bug has been fixed in the meantime.
Without updating this issue or, AFAIK, telling anybody about it.
Moreover, this issue has now been closed with resolution "Cannot Reproduce".
Hahaha...
Don't get me wrong. I'm happy this is working again!
But not only was Atlassian's response to this issue inappropriate, they sadly didn't even use the super-easy opportunity of saying "Hey guys, look, we fixed it for you!"
That just shows that awareness of the relation between reported issues and development isn't where it should be. And that's not only to the detriment of end-users but in this case also directly to Atlassian.
I know that this isn't an easy nut to crack. But Atlassian isn't some obscure one-person show either. If it were only this issue, you might consider it an outlier. But rather it seems to be a pattern observable in so many reported issues.
Given that technically, in all likelihood, this was easy to fix, it seems some process improvements would be required.
It's just sad to see how this went down!
I just tried and also wasn't able to "reproduce" the bug I had initially reported.
In other words: this bug has been fixed in the meantime.
Without updating this issue or, AFAIK, telling anybody about it.
Moreover, this issue has now been closed with resolution "Cannot Reproduce".
Hahaha...
Don't get me wrong. I'm happy this is working again!
But not only was Atlassian's response to this issue inappropriate, they sadly didn't even use the super-easy opportunity of saying "Hey guys, look, we fixed it for you!"
That just shows that awareness of the relation between reported issues and development isn't where it should be. And that's not only to the detriment of end-users but in this case also directly to Atlassian.
I know that this isn't an easy nut to crack. But Atlassian isn't some obscure one-person show either. If it were only this issue, you might consider it an outlier. But rather it seems to be a pattern observable in so many reported issues.
Given that technically, in all likelihood, this was easy to fix, it seems some process improvements would be required.