Feature Request: Create subissues instead of issues

[khalido]

I would like to make a User Feedback Issue (or bug drop can) and have all submission via bugdrop created as subissues under that parent issue.

Required: Have a Parent Issue ID in configuration

[neonwatty]

Thanks for the request. A few design questions before we implement this:

• Is self-hosted-only support acceptable? The likely implementation would use worker config such as PARENT_ISSUES='{"owner/repo":123}', keeping the default behavior unchanged for everyone else.
• Do you specifically need this for the hosted widget? If yes, we’d need a different design, because public script-tag config for parent issues is more abuse-prone.
• Should the config use the visible issue number, e.g. #123?
• Should this be per repository, or one parent for every repo served by the worker?
• If BugDrop creates the feedback issue but GitHub rejects adding it as a subissue, should submission still count as successful?
• Should BugDrop fall back to standalone issues when the configured parent is missing, closed, or inaccessible?

[khalido]

Hi, thanks for the reply - thinking through this:

• Self hosted is fine. Would be nice to have in your hosted widget too, but I see that gets more tricky.
• Yes to using the visible issue number, e.g. Add optional auto-include screenshot mode #123` - this stays consistent across issue changes and renames
• I would like it to function per repo. So each repo gets its own parent issue e.g "Bugdrop User Feedback"
• I use the gh cli to create subissues, that works fine, so this should too. If subissue creation fails, that should return an error. This would probably be a setup issue, right? So on the first time, I make sure a sub-issue is created. Once that flow is working, then it should just work.
  • falling back to standalone issues here could be an optional configurable item