Skip to content

How to use PyGitIssue2Todoist

Humberto Sanchez II edited this page Mar 29, 2025 · 1 revision

How to use PyGitIssue2Todoist

The idea behind PyGitIssue2Todoist is that a developer created issues in GitHub repositories. The developer then wants to see those issues in todoist as tasks.

The preferred way to use PyGitIssue2Todoist is for a developer to group issues via GitHub milestones. PyGitIssue2Todoist has several strategies for organizing the Todoist tasks

Todoist Strategy - Project by Repository

This strategy creates projects for each GitHub repository. This is ideal for developers who have purchased a Todoist license which allows unlimited projects

PyGitIssue2Todoist initially creates a project in todoist with a name that matches the repository name. For each selected milestone, that has issues PyGitIssue2Todoist creates a todoist task by the name of the milestone. The issues then are subtasks in the todoist milestone task. See the following image.

ProjectByRepository

Via the user interface the developer selects issues from milestones that are then cloned to todoist. Note the following screenshot.

RepositoryMilestoneIssueSelection Selecting from All simply copies the tasks directly to the newly created todoist project

Todoist Strategy - Single Todoist Project

This strategy creates repository tasks under a single top level project. This allows developers who are using the 'community' version of Todoist to create sub-tasks for all their repositories inside a single top level project. 'Community' users are limited to five Todoist projects.

The selection mechanism is identical to the 'Project by Repsitory' strategy. The following shows the location of the tasks for 2 different repositories and a single milestone each.

SingleProjectByRepository

Todoist Strategy - All Issues Assigned to User

This strategy relies on a GitHub issue selection strategy that collects a developer's open issues across all selected repositories and organizations. Once they are collected the developer can choose to clone them all or only a selected subset.

Thus, the PyGitIssue2Todoist selection user interface is simpler as illustrated in the following image.

AllIssuesAssignedToUserSelection

PyGitIssue2Todoist prepopulates the repository selection list during startup. At this point, the developer can select all the repositories to query or a subset. The developer initiates the GitHub retrieval process by pressing Retrieve Issues. Depending on the number of queried repositories and the number of issues this can be a lengthy process. As such, PyGitIssue2Todoist, displays a progress dialog while the process complets. Once the developers clones the tasks and pressed Create Tasks, PyGitIssue2Todoist displays a task creation progress dialog as this can also be a lengthy process.

Strategy Configuration

The developer picks the todoist strategy via the PyGitIssue2Todoist→Configure dialog as depicted below.

StrategyConfiguration

Changing strategies requires a PyGitIssue2Todoist restart. It is not wise to mix strategies.

Clone this wiki locally