wgc1929 I don't think that recreating the issue will give it any more attention. Unless the recreated issue is significantly different than this issue, then the recreated issue will be resolved as a duplicate of this issue.
The description of this issue says:
when looking at the "Tags" tab of those jobs, they still show (subjobs for) tags that are way older than 7 days.
The later discussions in the thread seem to align with that phrase. They want to remove tags from the list of jobs if they are older than a threshold. When a tag is removed from the list, it won't be built.
In terms of getting attention, the most effective way for an enhancement to get attention is for someone to implement the enhancement, test it for their own use, then submit it as a pull request. Others can then test the pull request as well and report their experiences with the incremental build of the pull request.
I'm happy to have users express their interest in a feature, but that doesn't get us any closer to an implementation of the feature.
OK, maybe I need to clarify further. I'm referring to tags that have actually been built. As opposed to branches, tags will most likely not go away again, so a multibranch pipeline collects subjobs for all the tags it has ever built. My request is that jobs for those tags that would now be ignored because of their age be removed again.