{"id":2664,"date":"2013-01-27T13:11:09","date_gmt":"2013-01-27T13:11:09","guid":{"rendered":"http:\/\/sl.governormarley.com\/?p=2664"},"modified":"2013-01-27T13:11:09","modified_gmt":"2013-01-27T13:11:09","slug":"jira-requires-some-changes","status":"publish","type":"post","link":"https:\/\/sl.governormarley.com\/?p=2664","title":{"rendered":"Jira Requires Some Changes"},"content":{"rendered":"

I’ve just reluctantly filed a Jira issue on something fairly trivial, but something that’s not working correctly for me. I say reluctantly because I still find the changes to the Jira in September<\/a>, extremely disappointing. I actually pondered whether to both filing a report because the whole process is now so disappointing. The only real improvement I see is that it’s now easier to report an issue because they’re mostly filed under the Bug report project but beyond that, it’s an unsatisfactory experience.<\/p>\n

One area where it is partcularly disappointing is that you no longer even get feedback on your report that the issue has been fixed, to quote the September blog post:<\/p>\n

“Once a Bug reaches the \u201cAccepted\u201d or \u201cClosed\u201d status, it will not be updated. You can watch the Release Notes to see when and if a fix has been released for your issue.<\/em><\/strong>”<\/p>\n

I’m sorry, but that’s a really poor approach to something which is a two way street, people take time out to report an issue, they should certainly be alerted that a fix has been released from their initial report, to not do so is really poor form and is one of the issues that caused me to ponder whether or not I should bother reporting the current issue I’ve observed.<\/p>\n

<\/p>\n

Another quote from the September blog post:<\/p>\n

“Second Life users will only see their own reported issues. When a Bug reaches the “Been Triaged” status, they will no longer be able to add comments to their issue.<\/strong><\/em>”<\/p>\n

Now ignoring the first part of the quote, which is in itself horrid, the second part is where my last reported Jira issue sits. That one has a status of Been Triaged. However the thing is, it appears to have been fixed, so I wanted to add a comment to state this on my report, however as the quote states, you can no longer add comments when an issue has a status of Been Triaged. Therefore, to update my Jira I had to edit it and add that the issue seems to have been resolved, this was for my sake as much as the Lindens because now I can see that I’ve added a note to say it seems to have been fixed, it’s a note to myself as much as anything else.<\/p>\n

I can understand the frustrations the Lindens had with the Jira, the flame wars, the unhelpful comments. I really do appreciate that they want to cut the noise from the Jira, but as it stands it’s a very unsatisfactory experience. People report issues because it’s the right thing to do and they will continue to report isssues because it’s the right thing to do but the process really does need some revision and the very minimum should be that your Jira report gets updated when a fix has been released, you shouldn’t have to watch the release notes. The concept of not telling a reporter an issue is fixed is very poor form in customer relations.<\/p>\n

Tweet<\/a>
\n