Re: Issue tracking

Hi Dave

Hi

Sorry, I missed that update.

No problem, glad to see you are still here and thank you for the reply.

The tracker is part of the PostgreSQL project infrastructure, and thus the pgAdmin project has no control over the requirement to login to see tickets.

I know very little about the PostgreSQL project, so I cannot judge the control pgAdmin has over it, but for sure if pgAdmin's control is null, that will make solving more costly and difficult, so I tried to record that information in the ticket. Thanks

We are considering a move to Github issues, but that's a huge and complex task.

I would recommend against moving to GitHub's ITS engine, which is most basic.

The ticket I filed was set to Status "Rejected". Could someone either explain why or set that field to a more representative value?

On Wed, Nov 3, 2021 at 9:20 AM Philippe Cloutier <chealer@gmail.com> wrote:

Greetings,
After starting to use pgAdmin a couple years ago and struggling to track one of its issues, I figured out that its issue tracker was not publicly visible (an account is required to display tickets). I reported that meta-issue in report #5042.

The ticket's Status field was later set to Rejected. In August, I asked in that ticket if there was a reason for that.

In September, as there had been no answer, I specifically asked Dave Page, who is responsible for the field's change, if he could explain it. Unfortunately, more than a month later, that question remains unanswered, as can be seen in the following screenshot:

I am therefore resorting to this forum to request help from the pgAdmin community. Can someone either solve that or at least help elucidate? A quick look indicates that Mr Page still contributes to pgAdmin.

Thanks in advance

-- 
Philippe Cloutier
http://www.philippecloutier.com

--

Dave Page
Blog: https://pgsnake.blogspot.com
Twitter: @pgsnake

EDB: https://www.enterprisedb.com

-- 
Philippe Cloutier
http://www.philippecloutier.com