I see request in jira like: "index.php?/ext/jira...issue={task id}...".
I need to get ids of runs, then parse runs from TestRail API.
Maybe there is an easier way to get that ids?
Related
I bought a nest thermostat as I thought it would be able to give me detailed data to showing the target temp and the actual as well as time etc. I needed this for various reasons.
However, it seems the official API "Works with Nest" was closed by Google. I've been able to get postman to ping the same location that the Google Nest Webapp hits and get back the data I need. I want to create a simple webapp to keep polling and save the data locally. However, I'm unable to find the OAuth Client Secret that the Nest Webapp uses to get the authorization code. I had to login via the webapp to get the code in one of the request and then test it out using postman.
Is there any other API that will allow my to poll this data for my Nest easier?
If there isn't another API, is there a way to get the Client ID and Client Secret form the Nest Webapp so I can drop that in mine to use? (I know its hacky, but am I think I'm out of options)
I know how to get all builds from a specific job and know how to get the list of builds from the current user in the Jenkins UI by going to https://jenkins.${domain}.com/user/${username}/builds, however, there doesn't seem to be an API for that specific address because if you go to https://jenkins.${domain}.com/user/${username}/builds/api it comes up with a 404.
Is there a way via the api to query all of the builds for a specific user?
I am assuming this is not possible but hoping it is.
I am using https://developer.atlassian.com/bitbucket/api/2/reference/ and trying to retrieve all tasks for a particular pull-request, but I can't figure out how.
Is it possible on Bitbucket Cloud (bitbucket.org)?
This is not currently possible - as I type this, the API returns the count of open tasks for a given PR (task_count in https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/pullrequests/%7Bpull_request_id%7D), but not the content of those tasks.
It is not documented but, it works by sending GET call to below endpoint
https://api.bitbucket.org/2.0/repositories/TEAM/REPO_SLUG/pullrequests/PR_ID/tasks
I want to get updates from asana inbox directly using asana api.
Is there any way this can be done using api as i am unable to find anything in api documentation. If there is anything that i might have missed in api please point me to that.
Unfortunately, we don't have an endpoint for the inbox. As was discussed in another question, you may be able to get this by grabbing every task across all projects into a local database. You would then need to search for tasks where assignee_status is set to inbox.
We have two jira installations at our company. One that we use for our projects and a second one for testing purposes.
I'm working in a project that needs to use the JIRA REST API. For this purpose I'm connecting to our testing instance.
The problem is that while trying out the REST API, I keep getting 400 errors without a single explanation of what went wrong. I just get an HTML with
Your browser sent a request that this server could not understand
I was a bit desperate and decided to try it into our real JIRA. To my surpirse the same request gave me a different response:
{"errorMessages":[],"errors":{"project":"project is required"}}
In this case, I do get a meaningful error!
I replicated this easily. I would never get a meaningful error from the test instance, but the real one will always give me one.
I cannot keep trying out stuff in our productive JIRA, but I cannot easily continue working without getting meaningful errors. So, what could be wrong in the testing instance? I could not find any configuration about the 'verbosity' of the API responses.
I believe that this error is returned not by JIRA but rather by proxy web server that is part of you production configuration.
I suggest you to compare HTTP headers that are sent with working requests from your browser with headers you pass via curl. Googling for the "Your browser sent a request that this server could not understand" helps too