Implement the JIRA Software REST API Reference
See original GitHub issueFrom what I saw from the code, the GreenHopper implementation is a bit dated and does not use much of the API available on the JIRA Software REST API Reference.
The advantage of this would be that we would have access to a clean json allowing to access agile data, instead of custom fields. For instance the get issue method allows to get information about the epics of the sprints without needing to go through custom fields. Finding information about the sprints of a story can be especially cumbersome as one can read on the “JIRA Software field input formats” section of the JIRA Cloud REST API Reference
I came across this problem as I was trying to write code to propagate Stories and Epics from a source project to a target project, where I have three sub teams, which need to have three separate backlogs. I know it is ugly, but can’t have the same backlog for a sub-teams doing NodeJS, another one doing iOS and a last one doing Android. Technologies are too different. /) Hopefully I get the time to finish this code and open-source it 😃 .
From what I saw, it might be a good idea to leave GreenHopperResource
as it is and create an AgileResource
, from which the following resources could inherit:
AgileBoard
AgileEpic
AgileIssue
AgileSprint
I have started a project on this at https://github.com/esciara/jira/projects/1 . If this is not the best way to move forward with this, please shout. Any constructive feedback welcome.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top GitHub Comments
is there a way to access the agile boards and sprints without using the greenhopper api ? .boards returns an error from the client code jira/client.py:2761 “Warning: Old private GreenHopper API is used, all parameters will be ignored.”
ah ok … i found i needed to set options a la…
options = { ‘server’: “URLHERE”, ‘agile_rest_path’: ‘agile’ }
leaving this here in case other people have the same issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.