Implementation of Atlassian Jira as new issue tracker option #516

Merged
merged 1 commit into from Jul 29, 2013

Projects

None yet

4 participants

@xenji
Contributor
xenji commented Jul 4, 2013

The implementation is based on the abilities of the ReST API v2, so everything above Jira 5.0 is supported. This implementation supports only the HTTP Basic auth, not the OAuth version. This would have lead to severe changes in the user management, too.

I encountered, that adding new field (I needed some new) has to be done in the parent IssueTracker class. Is there another option to do this? I would like to have the fields bound to the Jira Tracker implementation, but if I do so, the rendering fails with an error of not finding the fields.

Kind Regards,
Mario

@xenji
Contributor
xenji commented Jul 4, 2013

I just saw the #448 ... Damn :D

@coveralls

Coverage Status

Coverage remained the same when pulling 2d86e4f on xenji:feature/jira-issue-tracker into bf7175e on errbit:master.

@shingara
Member
shingara commented Jul 8, 2013

Can you add some documentation please ?

@simonoff
Contributor

Very important addon! Please finished it.

@shingara shingara merged commit 2d86e4f into errbit:master Jul 29, 2013

1 check failed

default The Travis CI build failed
Details
@shingara shingara referenced this pull request Jul 29, 2013
Closed

JIRA Issues support added #448

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment