[16:07:13] <paulproteus> Or wha does "{tracker_name}" mean?
[16:07:15] <mollydb> yeah
[16:07:19] <paulproteus> You write the literal string
[16:07:22] <paulproteus> {tracker_name}
[16:07:25] <paulproteus> and what it means is:
[16:07:45] <mollydb> so i don't have to dig up some sort of thing somewhere that will say, like {edX_open_JIRA_issue_tracker03798523798235708325}
[16:08:10] <paulproteus> When this thing discovers JIRA issues, it will assign them to an open source project whose name is the same as the name of the thing that you are configuring.
[16:08:47] <paulproteus> The "tracker" (which is to say, this configuration data you're creating, for the bug downloader) by default has the same name as the project you're attaching the tracker to.
[16:09:14] <paulproteus> The reason this is so complicated is that some projects have a few bug trackers so then they need different "trackers" on the OpenHatch site, each of which might have different names.
[16:09:28] <paulproteus> Although really now that I think about it, they should not have names; they should just have descriptions.
[16:13:19] <mollydb> nods
[16:13:21] <mollydb> cool
[16:13:30] <mollydb> i'll add that to the documentation tomorrow, if i remember it
[16:13:52] <paulproteus> Great (although arguably I should beat you to it by making the corresponding product change so it's just not that hard).
[16:14:10] <paulproteus> OK if I copy-paste this into an OpenHatch bug?
[16:14:39] <mollydb> sure
tracker_name is present in several dozens of files and is referenced in so many parts of the stack. :confounded: I'll attempt to remove it and update my progress here. :racehorse: Challenge accepted.
Relevant IRC copy-pasta: