Bumping github issues?

Is there a recommended procedure for ‘bumping’ github issues that dont appear to be getting any attention? [in my case, specifically https://github.com/kobotoolbox/kpi/issues/1971, which is rather an annoying ‘bug’ but should be a trivial fix]. Just want to follow correct protocol (and not piss anybody off) :slight_smile:

1 Like

Thanks for asking :slight_smile: I think this forum (vs. bumping on GitHub) is a great place to bring up languishing issues that are causing you grief. Would you be able to search for that GPS coordinates can only be collected when outside string in different repositories to see where it’s coming from? Based on a quick Google search, and a comment on a GitHub issue in the results, I think you’ll find it somewhere in https://github.com/XLSForm/pyxform. If that’s true, then we should move your issue report to Pyxform (and possibly mention it on the ODK forum to get the ball rolling).

1 Like

Hm. Just tried it again and the hint no longer appears in either Kobo’s exported XLS nor XML. So apparantly somebody already fixed it somewhere! :slight_smile: