Replied to a tweet by curried apotheosis (Twitter)

A frequently recurring product wish I have when interacting with issue trackers: labels that I can add to issues, and only I can see.

They're for my organization and tagging. That's it.

Not going beyond "me" is a *feature*.
— curried apotheosis (@warpfork) January 8, 2020

I do something like this on my own website. Post issues there so I can own the data (and tags) and control the details and notes and syndicate a copy to GitHub. I’ve documented some of it here: Enabling two way communication with WordPress and GitHub for Issues. Others have done it as well: I’m sure there are other ways of doing this, but it works well for me and just for the reasons you describe.

If others want to see my details, the’re available on my site (when I make them public), but they’re primarily for my benefit and not others. The public copy conforms to the silo’s requirements and can be modified by the repo owners, if necessary.

Bookmarked at 2020/01/10 9:51:41 pm