I guess the answer is probably no.
Sure, I can imagine kludges to achieve this. For example, I could create a project called “Future Issues” which I would periodically check, and from which I would manually move issues to a project called “Current Issues.”
You could maybe use issue due dates for this? I don’t think you can filter issues to see only the ones that are past due, but you can sort so they’d be on top.
In some todo apps it’s called snooze button for tasks. I call it the “just do it tomorrow” technique. I do this with my personal things. I add a future date to items and they bubble up in a simple dashboard that just sorts them, nothing fancy. Unfortunately, gitea doesn’t allow to add metadata to issues nor sort by metadata. But we can store metadada externally to gitea.
Presumably, issues on gitea (and github) have immutable IDs, so we can just request a list of tasks and store them along with the future-date metadata. And then write some kind of view that sorts issues for us.
I’ve written a proof of concept for this in org-mode in emacs and it works fine. I’m not sure if anyone is interested in using emacs for this except me, but here’s how it works: a task is a heading, it has an inactive timestamp. Then we ask emacs to sort headings. That’s it.
I guess this can be done as easily by writing a simple web server or a cli tool that would get a list of issues and store metadata somewhere, but my way is way cooler, because I can edit headings manually and store this org file in git.
I wish we could just work with metadata directly in gitea though.