"Schedule publishing" to a different category

We’re experimenting with a category where only staff can create new topics but everyone can reply. We post a weekly discussion topic on Mondays & for next week, I’d like to “promote” a topic initially created by a user.

I assumed I could schedule publishing for Monday like I did for this week’s topic.

But that’s not available on his post:

Because… it’s not starting from a private category?

Which… I guess I understand since I suppose “publish” means “make public” here.

And, in my case, I want to use the feature to “make more public”.

So this is my request to broaden the feature :smiley:


As you know, I reckon, you can’t schedule publishing to same category, because it is… already published :wink:

Actually Discourse doesn’t have scheduled publishing. It has scheduled move to another category, what is called as scheduled publishing.

Bad UX, I think.

But I’m quite sure the team doesn’t change that too fast (they have tendency listen you, though :wink: ) so use it more ”expected” way: publish it first in staff-only category and schedule it with moving to users-reply category. Problem solved.

If I now understood right you…

1 Like

Yep. I want to move it to another category. :wink:

The thing is, I wan’t to “publish” a user’s post to another category as a way of heightening the attention it gets.

Is there anything stopping you from moving it to a more private category prior to scheduling publishing?

Ehm… I thought about that. But I’m hesitant to move a user’s post to a place he wouldn’t be able to find it (yes, he can track it down through his user activity, but…)

We have a core principle of transparency, and a move feels like it would go against that.

1 Like

As scheduled publishing only moves a topic anyway are the two so different?

It’s going to be moved when it’s published regardless?

I don’t follow now :flushed: Because…

What is the issue if you allow that category only (writing/reading) for staff and then you will schedule it to category, where topics are allowed only for staff and replying for everyone else?

Ehm… Yes?

Because I can’t schedule this, then I’ll be moving it manually. I had hoped to “set it and forget it”. And without the ability to schedule the move ahead of time, I have to remember to do the move on Monday.

The issue is that I can’t schedule it.

To be clear, the target category is

1 Like

Right, but your choices are to move it from the current category to a category where it can be scheduled from, or to wait until scheduled publishing allows it to go direct from current category to published category.

The option to schedule publishing is tied to the permissions of the source category, not the destination.

Either way the user will see their topic move categories, no?

It is already published. It doesn’t matter any more. Just move it.

But you’ll be in same situation on monday. And week after that, and so on. And that issue you should fix, not worry some trivial moving now :wink:

I truly don’t understand this. I can’t schedule the move. That’s my whole point. So I’ll have to remember to do this manually on Monday with no extra help from the platform.

And yes, the user will obviously see the move. In fact I PM’d him yesterday to explain what we plan and why.

I’m asking for the ability to set up the move when I’m thinking about it, rather than having to remember to do it later. I’m sure you’ve never forgotten something you meant to do, but I have.

Ok, but the issue is the source category where the post currently resides.

What’s stopping you from moving it so that you can schedule it?

Moving it so I can schedule it means moving it to a non-public category, which I don’t want to do. Maybe someone will come across his post in the meantime and give an answer (probably not, but it could happen). I don’t want to prevent that. And as I said earlier, I don’t want to put the user’s post in a place that he, himself wouldn’t be able to (get to to) find it in.

1 Like

I quite like this, and can see it being useful to promote announcements from a restricted public to a more general one like you describe.

1 Like

Actually @Falco I want to do the opposite: promote from an open-to-all category to an “exclusive” one.

1 Like