This Jira Message Is Wrong!

Jira No Entry

This the message one sees when they try and look at someone else’s bug report in the new and improved Jira. There is of course temptation to contact the Jira administrators that this message is wrong, and surely they know it’s wrong, it’s certainly wrong headed, but as it’s an intended consequence of Jira 2 – Electric Boogaloo, complaints are likely to fall on deaf ears.

There’s a thread over on the official forum, entitled : New Jira System Worhless. The new Jira system is not worthless, it’s a big backward step for end users who were used to the old Jira system, worthless is too strong, it’s just a bit rubbish for those who knew how to search the Jira and look for results. Howevere there are many valid points within that thread.

As an example, someone points out that they don’t even know what the resolutions mean, although this is by no means a new issue, people don’t know what “Released” means in terms of a resolution. A system that does not inform end users of the status of issues in an easy to understand fashion is not working as intended.

Drongle McMahon notes: “Somehow I doubt that. My jira BUG-101 was submitted 14th Sept. It was marked as Resolved; (Status Accepted; Resolution Released; Fix Version/s None) on 17th Sept. It is not fixed in the latest beta viewer (266708, Nov 7th). I’d love to invite you to look at it, but of course you can’t. I have to agree with Gadget, that the jira is now essentially useless to anyone other the select few with privileged access. It doesn’t even give worthwhile feedback to the submitter, let alone the rest of us. I don’t see any point in contributing to it in future.

A system that discourages people who know how to submit bug reports from using it, is not working as intended, unless the intent is to stop people from reporting bugs, which would certainly improve stats on reported issues, but it wouldn’t be helpful overall.

Moon Metty tried to explain the terminolgy on the new Jira: “Accepted” means that the bug is confirmed. “Released” means that ummmm … the bug can roam freely in its own antfarm, lol. (It’s nonsense)

Cerise Sorbet adds: “On the new system, “Released” only means that the bug was copied into one of their internal projects and will be worked on. After that, it is a black hole.

The only way you will know that bug has been fixed is if server or viewer release notes have a line specific enough that you can tell it’s your bug they are talking about (not likely, as most LL release notes are pretty vague), or the problem goes away.

I mean, this really is poor form, Drongle McMahon, Moon Metty and Cerise Sorbet are experienced users and even they are pouring scorn on the new system and I can see why, Linden Lab have tipped the balance too far the wrong way. Previously people complained that the Jira was cumbersome and difficult to use for reporting bugs. The Jira was never intened to be a support arena, it was intended for people who knew how to report bugs. However over time support started telling people to go and file a Jira report, so it became an extension of support. Support could also refer people to Jira’s, which of course they now can’t do so often as the great unwashed can’t see other people’s reports.

The only positive about the new Jira is that it’s easier to submit a bug report. However, as the resolutions are confusing even to experienced Jira users, the process will be equally, if not more, frustrating for end users. This is a bad idea.

If you have some constructive feedback to provide about the new Jira, fill out the following survey:

Leave a Reply