The Communications Hub User Interface (CHUI) viewer has done something interesting with the Jira, it has made CHUI issues viewable to all, unlike the wretched new Jira in general which limits reports and requests to only the person who submitted the bug, Lindens and a select few residents.
The advantages of this are highlighted in a forum post in the official forums. Hitomi Tiponi asks where the promised survey is and gets a response from Viewer Linden (probably a cousin of Commerce Team Linden):
Hi all. We did indeed plan to release a survey, but a number of residents have submitted not just bugs, but general opinions, in JIRA. As JIRA seems to be working well for feedback, we may not release a formal survey after all.
Since releasing the project viewer, we’ve been working on a critical piece of CHUI, the notification subsystem. IN CHUI, you’ll have more flexible and more diverse options for being alerted of incoming communications. We’ve also been using the feedback we’ve received so far in our ongoing work. You can expect the next project viewer, which will include these new functions, by the end of December.
You should feel free to file JIRAs for any feedback you wish to offer. In particular, we want to know if the new functions (such as the conversation log) are usable and convenient, and improve the viewer communication experience. We also want to know if you think the reorganization of the communication functions will help new residents get up to speed more quickly. However, any and all feedback you send us is of great interest to us.
Thanks everyone.
CHUI gets good feedback in the Jira because others can read the issues.
I have provided feedback on CHUI, even seeing someone else’s report and asking if the problem still exists because I could not reproduce the issue, the answer was, the issue has been fixed. I’ve also raised a Jira of my own in general recently, it may or may not be a duplicate, I don’t know if it is a duplicate or whether Linden Lab just duplicate the issue.
My issue is, for example, 941 and in the activity log it appears with a line through it saying it’s a duplicate of 945, which I can’t read to see if it is a duplicate! I don’t know what 945 is, which really isn’t helpful to me as someone who reported an issue. I’m also confused as to why 941 would be a duplicate of 945 as 945 is a higher number, but there you go, without being able see 945 I can’t even start to figure out what’s happening.
However with CHUI, where I can see other bug reports and check for duplicates, it seems to be working well. I have no idea why Linden Lab have gone down this path with the Jira, but it really isn’t helpful to hide issues, especially when they’re supposedly duplicates.
I can guess at why 941 was considered a duplicate of the later 945. As the JIRA items are read they pick the one in the set they are reading that best describes the problem or has the most attachments.
Well if I could see 945 it would make more sense, merging issues is the sensible thing to do, so is making the one that best exemplifies the issue the main report, but denying a reporter access to the merge is a tad off.