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

Add some kind of "Health Check" for bug tracker integration (Jira) #97

Open
okainov opened this Issue Nov 2, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@okainov
Copy link
Contributor

okainov commented Nov 2, 2017

I've added our Jira into Admin, so links to bugs work good. Trying to understand what can Kiwi do, I've also added Base URL (https://ourjiraaddress.com/) and API URL (https://ourjiraaddress.com/rest/api/2/project/ourprojname), filled login and password, but even when I mark a checkbox "Check to add Test Case(s) to Issue Tracker" from test run, looks like nothing happens. No any error appears.

It would be nice to have some kind of "health check" in issue tracker Admin page to make sure that everything was entered correctly.
As an idea, it could be something like "Check that Kiwi can read issue details" by given URLs, credentials and (for check only) issue number.

Purpose: to be sure that integration works in general without guessing where the error is.

@atodorov

This comment has been minimized.

Copy link
Member

atodorov commented Nov 3, 2017

note to self: indeed the configuration of external bug trackers is a bit tricky and very vaguely documented. I will add the necessary docs, also describing why you can't reset the Tracker Type back to null and how to configure authentication.

@GodfatherThe a health-check button would be the best I think but I'm not sure how easy is this to implement. I will have to take a look at it.

@okainov

This comment has been minimized.

Copy link
Contributor

okainov commented Nov 9, 2017

Potential stages which can be checked:

  1. Just connection \ trying to create Bug Tracker object (i.e. jira.JIRA). Problems which may be found here - wrong address, missed "https" in address, wrong configured proxy (especially not obvious - it was required to unset http_proxy to be able to access JIRA in internal network), wrong credentials. I personally met all of those problems when I was trying to configure it.
  2. Trying to get issue details. Input from a user is required "Please input some issue ID from your project and click ". Problems which may be found here - no access to given project for given credentials.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment