The CKAN Technical Team reviews new issues twice a week. They aim to assign
someone on the Team to take responsibility for it. These are the sorts of
actions to expect:

If it is a serious bug and the person who raised it won’t fix it then the
Technical Team will aim to create a fix.

A feature that you plan to code shortly will be happily discussed. It’s often
good to get the team’s support for a feature before writing lots of code. You
can then quote the issue number in the commit messages and branch name.
(Larger changes or suggestions by non-contributers are better discussed on
https://github.com/ckan/ideas-and-roadmap instead)

Features may be marked “Good for Contribution” which means the Team is happy
to see this happen, but the Team are not offering to do it.