question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Implement the JIRA Software REST API Reference

See original GitHub issue

From 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:closed
  • Created 7 years ago
  • Reactions:3
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

15reactions
atiniircommented, Mar 5, 2018

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

0reactions
stale[bot]commented, Oct 15, 2019

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

JIRA Server platform REST API reference - Atlassian
Welcome to the JIRA Server platform REST API reference. You can use this REST API to build add-ons for JIRA, develop integrations between...
Read more >
REST APIs - Atlassian Developer
The Jira Server platform provides the REST API for common features, like issues and workflows. To get started, read the reference documentation: Jira...
Read more >
The Jira Software Cloud REST API - Atlassian Developer
Welcome to the Jira Software Cloud REST API reference. You can use this REST API to build add-ons for Jira Software, develop integrations...
Read more >
The Jira Cloud platform REST API - Atlassian Developer
The Jira REST API enables you to interact with Jira programmatically. Use this API to build apps, script interactions with Jira, or develop...
Read more >
Jira Server platform REST API reference - Atlassian
Welcome to the Jira Server platform REST API reference. You can use this REST API to build apps for Jira, develop integrations between...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found