Follow internal case number reference or database?

[PeteS]

If there is a better place for this, admin, please move, but this seemed as good as any I could find. OR if this already is addressed, then point me in the right direction.

Quite often a bug I report turns into an internal case (CPANEL-12345), and also many times involves a temporary work-around. The problem is that I know of no way to track these so I know when the real fix is rolled out and I can take appropriate action.

I know that I can continue to look for the case numbers in releases (not fun and has become too cumbersome to manage), and often a cPanel rep on here will say they will post back when it is resolved (usually happens, but easy to miss even though I follow every thread I post that this relates to, due to the number of them).

It would be super helpful, and I think easy enough to do, if there was a way to "follow" an internal case by case number. Certainly you already track which cases were included in which releases. So how this would work is that we could enter a case number(s) in an interface and it would show it as "pending" (not released) or "released" (showing the release number(s) behind that. Then we could visit that page, sortable by released date, and by case number.

Please...?

-Pete

 

[LucasRolff]

So following the changelogs should be pretty simple - it's a matter of searching for the case ID.

However, if you've created a ticket regarding the given bug, you can always ask for the support to be notified whenever a release is made ( I think this actually happens automatically ) - then you'll receive an email whenever a bug that you've had a ticket about has been resolved.

 

[cPanelLauren]

We don't release any case details as far as the process, we only post to Change Logs - Change Logs - cPanel Documentation to update as far as when an issue (CASE) is resolved. You can also follow our RSS feed there.

If you have an issue that was brought up here in the forums, you'll notice we modify the prefix of the thread to "In Progress" then to "Pending Publication" and then "Resolved" during the process of resolution - we also do our best to update those and if you're watching the post you should get a notification in the event the issue is resolved or any updates are made to the thread.

 

[PeteS]

I appreciate what you both have said, and that's what I am doing now, but things get missed/forgotten/overlooked. The solution is for a case number list (that is of interest to me) to be kept "somewhere." Then the second part would be a way to view whether those cases have been resolved and the fix released in an update. I *can* keep such a list, *and* do a manual search for them periodically but it is cumbersome at best.

I don't have the resources (access to the case data) to automate this, but cPanel does. Wouldn't it be a decent idea to have the ability to follow a case number, just as we can a thread, and be notified when it is fixed and released? This seems in everyone's best interest, and also seems not too difficult to implement. If not an interface (on this forum, or somewhere), how about at least a forum here where each active case gets a post when created, and a post when fixed and released? Disallow commenting, so it is read only, but we could follow it, which would do what I ask as far as being able to sign up for notifications.

The primary use case that has brought me to this is when a bug get discovered, and will be a long term fix, so a work-around is provided and implemented, but it would be desirable to remove the manual work-around once not needed. Even though I follow a thread or feature request related to it, it is easy to overlook a post to it that announces the fix, and/or forget that a work-around was put in place for a particular bug. I hope that makes sense...

This isn't a cPanel feature request or I would create one there, so I am doing it here. Please consider...

-Pete

 

[PeteS]

So following the changelogs should be pretty simple - it's a matter of searching for the case ID.

Unless I am missing something, the problem is that there is no single location to search, since each release versions is its own post (as it should be) so we can research the changes by version. But we can't go the other direction and search by case number to see if/when a case fix was released. It would require searching all past change log post individually for a each case number,which is too cumbersome.

-Pete