#7151 [Ask Fedora] Unable to approve post in moderation queue
Closed: Fixed Opened by ankursinha.

  • Describe what you need us to do:
    There is currently a post in the Ask Fedora moderation queue that none of us admins/mods are able to approve: https://ask.fedoraproject.org/en/moderation-queue/

We're not really sure what's happening here. Upstream may need to take a look.

  • When do you need this? (YYYY/MM/DD)
    When convenient.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    NA

  • If we cannot complete your request, what is the impact?
    I'm going to message the user that posted the message and ask them to post a fresh question. Hopefully that one will go through.

@mattdm: Is it ok for us to file Ask Fedora tickets here? If there is a way for us to inform upstream of these tickets directly, that would make things easier? Could we get them to set up an FAS account that we can tag, for example?


They have asked us to mail requests to support@askbot.com

Ah, so is it OK for us (all mods/admins) to first file a ticket here for tracking purposes, and then inform upstream at the abovementioned e-mail address? (Does someone need to be CC'd?)

Or should we ask the admins/mods to file tickets here, and a few of us can e-mail upstream letting them know---maybe a weekly e-mail instead of individual e-mails for each ticket?

Another alternative is to file tickets on Ask Fedora with a "meta" tag, but then all users can file them so they won't go through a filtering process where we get to look at them first.

Well, I am not sure tracking them here does much good? I suppose it could let us avoid mailing duplicate issues upstream, but otherwise we have no way to get status or usefully track the issue.

@askbot Any thoughts? Can you look at this issue and then let us know if tracking here is of use, or if we should just ask everyone to email issues?

No worries, we can track the issues here. Will update you soon.

I've found the post that can't be approved, will need to take a second look. There is something unusual about this particular post.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

I'v approved this post, now working on resolving the issue permanently.

I'll go ahead and close this now, unless there's some reason to try the perm fix here?

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata