Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync Redmine versions/issues with Github milestones/issues #6

Open
rthrash opened this issue Sep 17, 2013 · 0 comments
Open

Sync Redmine versions/issues with Github milestones/issues #6

rthrash opened this issue Sep 17, 2013 · 0 comments
Assignees
Milestone

Comments

@rthrash
Copy link
Owner

rthrash commented Sep 17, 2013

Redmine uses issues and assigns them to versions. Github uses milestones for the versions. Would be great to maintain this data, if relatively straightforward.

Rm API: http://www.redmine.org/projects/redmine/wiki/Rest_Versions
Gh API: http://developer.github.com/v3/issues/milestones/

Implementation notes

Retrieve all Redmine versions (version) for a project (project name): name, description, status, due_date, fixed_version_id
note: fixed_version_id is the ID of the Target Version (previously called 'Fixed Version' and still referred to as such in the API)

Create Milestones in Github: title, state, description, due_on, milestone

In Redmine you can list the versions. :ID can be either the integer ID of the project or the short URL identifier (e.g., "revo"):

GET /projects.xml
GET /projects/:ID/versions.xml

In Github, you can list milestones (to check if they exist first) with the following. Assign milestones by ID, not the milestone name/title:

GET /repos/:owner/:repo/milestones

Finally, if we want to maintain any other statuses, or other data, we need to push them to labels in Github.

@ghost ghost assigned mkschell Sep 17, 2013
@ghost ghost assigned CaptObviousman Nov 8, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants