Best practice forum (Archived)

Read-only bug tracker access for subscribers

I asked the question a little while ago but I guess it's better to give it a thread of its own. Would it be possible for Totara to provide read-only bug tracker access to subscribers please? The benefits of this would include:

allowing subscribers to check whether something is already identified as a bug before reporting it to their partner
identifying what the current status of an existing bug is (target version, updates on progress, etc.)
allowing subscribers to more accurately assess the items included in each release by referencing the bug ID in the release notes to actual details.

I appreciate that it wouldn't be appropriate for subscribers themselves to submit or edit bugs (since this is currently one of the privileges afforded to partners), but I think read-only access would be a reasonable compromise.

Thoughts?

Dan

Permalink | Reply

The content of this forum post has been removed and can no longer be accessed.

Permalink | Show parent | Reply

Hi, it does seem like a good idea at first glance. However, in our experience to date we are appreciative of the wide range of contexts that subscribers have, including technical skill-sets and understanding of the context of developing software.

While of course there's nothing to hide, our bug tracking system is an internal system and if opened up would create another level of process and communications. From previous experience we believe it would lead to unintended confusion over how work is prioritised. For the vast majority of subscribers the correct channel for support queries is through your Totara Partner. Most of them have read access to our bug tracker.

What I can ensure you is that our release notes will be improved to create greater context and background.

regards
Richard

Permalink | Show parent | Reply