When i create the Group filter for contact sub-type there are no results coming.
The like query is being generated as "civicrm_contact.contact_sub_type LIKE '%%'"
Please see the images below
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
Thank you for raising an issue to help improve CiviCRM. We're sorry about this, but this particular issue has gone unnoticed for quite some time.
We would like to ask you to help us out and determine whether this issue should be kept open:
If this issue is reporting a bug, can you attempt to reproduce on the latest version of CiviCRM?
If this issue is proposing a new feature, can you verify whether the feature proposal is still relevant? Did it get the concept-approved label? Have other people also shown interest? Could it be implemented as an extension?
If yes,
Is it something that you could help implement, either by sending a patch or hiring someone who can?
Please feel free to comment or re-open the issue. We understand that automatic responses are annoying, but as the project evolves, we need a bit of help to triage and prioritise the most relevant issues.
Thank you for your help
P.S. This is an automated message. See infra/gitlab issue 20.
@totten@josh do you know why this issue is closed? And why there accompanied PR is not merged nor got any feedback? This feels very inpolite to people, like me, who contribute to the community.
And why there accompanied PR is not merged nor got any feedback?
Because we have a shortage of reviewers in the community.
I share your feeling of frustration about that. I often have to ask/beg people to review my PRs. I don't know the solution, but that's the current situation.
Re the bot: I think it's a good idea to have a bot nudging us about old issues. There are probably many issues that are already fixed with merged PRs that we forgot to close.
@vakeesan26 it looks like you logged an issue & Jaap worked on a fix - but we missed the step where you test the fix & it got lost - I don't suppose you remember if you ever tested it. Obviously it was kind of Jaap to work on the issue you logged & it's a shame it fell between the cracks