Skip to content
This repository has been archived by the owner on Jun 27, 2020. It is now read-only.

Discovery: Jira Integration #2

Open
RobAWilkinson opened this issue Oct 2, 2018 · 1 comment
Open

Discovery: Jira Integration #2

RobAWilkinson opened this issue Oct 2, 2018 · 1 comment

Comments

@RobAWilkinson
Copy link
Member

RobAWilkinson commented Oct 2, 2018

Discover and documented a basic understanding of how a logged in user might be able to access tickets within a Jira workspace.

Feel free to create a free account on the Jenkins board in order to play around with things

This ticket is done when we have the ability to create other tickets for the work to be done

@kfrz kfrz changed the title Jira Integration Discovery: Jira Integration Oct 11, 2018
@RobAWilkinson
Copy link
Member Author

RobAWilkinson commented Oct 17, 2018

Took a beat and dug into this:

  • There is an access token/oauth flow for Jira, but you have to authorize the application on the CMS side. Maybe one day, but not today.
  • We can access the REST API by passing username and password however.

In light of this, it feels icky to be passing usernames and passwords and saving them to the server.

I would like to get the rest of the teams thoughts on just hitting the rest API from the browser, loading the data into the react app, and then sending it to the rails backend when the Week in Review is saved. This might work, I'm not sure how CORS is set up on the jira instances

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant