Initial TODOs

[justaugustus]

Initial observations

• OAuth 1.0a is legacy: Replace legacy OAuth 1.0a #31
• Document required token scopes: Document required token scopes #32
• Can you pass https:// in repo_name field? Can you pass https:// in repo_name field? #33
• Don't allow username/password auth: Don't allow username/password auth #34
• Support config format other than JSON: Support config format other than JSON #35
• Document dry-run operations: Document dry-run operations #36
• "Error: GitHub token required" even though token is in config file: "Error: GitHub token required" even though token is in config file #37
• Must specify --config, even though config was in default location $HOME/.issue-sync.json: Must specify --config, even though config was in default location $HOME/.issue-sync.json #38

Bugs / documentation gaps

• Usage examples: Usage examples #6
• Issue type is required: Error creating issue: issue type is required #7
• When updating issues, only first 50 Jira issues are considered: When updating issues, only first 50 Jira issues are considered #8
• Comment regular expression is fragile: Comment regular expression is fragile #9
• Issue with JIRA Cloud (Kanban): Issue creation fails with generic message #10
• Add unit tests: Add unit tests #11

Feature requests

• Add GitHub Project Board to Jira State Syncing: Add GitHub Project Board to Jira State Syncing #12

Patches to consider (from upstream pull requests): #13

Already completed

Move to Go modules: coreos/issue-sync#52

The go community (along with other associated tools) have moved on to using go modules as is it now built into the language. This issue is to track migration over to go modules (as opposed to glide).

Upgrade dependencies: coreos/issue-sync#45

Upgrade all dependencies

Clarify that sync is one-way: coreos/issue-sync#37

Potential fix: coreos/issue-sync#40

Change Readme: Clarify that this tool only syncs content from Github to Jira and not the other way around