I am trying to set the assignee field to an existing issue in Jira using the Rest api call.
I am getting the error: "Field 'assignee' cannot be set. It is not on the appropriate screen, or unknown."
I am making a PUT call to "https//:{jira-server}/rest/api/2/issue/OPCP-32" where OPCP-32 is the issue id.
Is it an error related to permissions or am I doing anything wrong?
My json looks like this: http://pastebin.com/56TMMTCN
It was a permission related issue. Got the necessary permissions and it is working as expected.
Related
I want to create a JIRA issue using Logic Apps when a row is inserted into a SharePoint online list. I've authenticated myself, but am getting this error. The main part of the message reads as follows:
Field ‘reporter’ of type ‘user’ is not supported. More diagnostic information: x-ms-client-request-id is ’71…’
The Logic App action is "create a new issue V2". The previous version seems to work OK, but has been deprecated.
The SharePoint list also has some rich text fields. Will I be able to upload them? Looking at the JIRA connector documentation I suspect not, but would like to check.
To resolve this, you need to remove the 'reporter' field from the JIRA Issue Type you are using in the Create a new issue task in Logic Apps.
I have encountered error, like images below
First i click login, the error not appeared
But when i login successfully, the application show error like this,
There is no mistake on Oauth Credential, but i think i miss a think.
This error appear just now, my application already run for 2 years
my scope on auth client is email..
Thank You..
There is a bug opened:
https://github.com/yiisoft/yii2-authclient/issues/241
Note that in the config you can set "returnUrl" => "...." so you can fix it without touching the code.
Probably there was some change from Google and now they return also scopes in the URL..
I just found the problem..
In Oauth2.php there is method called fetchAccessToken(), it set redirect_uri to 'http://yourdomain.com/site/login?scope=xxxxxxxx' using getReturnUrl() method, it adds scope parameter. I dont know why. so i set the redirect_uri staticaly and it works again.
now the question is why Oauth2.php is working fine before and now it produces that error? is there any changes somewhere maybe?.
I had a functioning setup. Then my admin made some Jira changes and now every time I do a checkin in PlasticSCM's Windows GUI I get the error message:
"Unable to log checkin data into issue tracker: The remote server returned an error (400) Bad Request."
Below is my configuration. I have tried removing the Custom Field ID but it still throws the error. What else can I try? How can I capture the request being sent? If I click "Test Connection" it is successful.
Unsurprisingly, the issue was on the Jira side. I got my Admin to make me an Admin so I could troubleshoot.
In plastic, get in a branch tied to a specific jira ticket. Check in a change so you get the error message. Good. Now, go to that Jira ticket. under the "Admin" button in the top middle, select "Add field". Find the field tied to the custom field number Id in plastic's configuration. If you followed Plastic's tutorials to set all this up originally, the field is called "Plastic SCM".
Now, it won't actually add the field, since the field is present on the page, but hidden because it has no value. You will see an "Edit" option. pick that. Enter any text like "Empty text". This is what is key, I think. It might be that the value was null, and now that you set it to an actual string, the field shows up. With this new text value, the Plastic SCM field should be displayed on the page somewhere. If you are still having trouble , choose "Where is my field?" from the admin button and look at the information displayed.
Now, make a minor change in your code and do a new checkin in plastic. No error message, right? Yay. Also, you should see check-in information displayed in the ticket now.
I know what you are thinking, sure, that worked for just one ticket, what about all the rest? Well, it seems like making this change has a cascade effect on other tickets in the same project, so you won't have to do it repeatedly. Weird.
We have two applications which use OAuth2 authentication to get access to Hotmail.
The first application works fine. But in the second application we have an error after entering login/password:
Server Error
404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
URLs and code used to show these URLs are identical in both application:
url = "https://login.live.com/oauth20_authorize.srf?response_type=code&redirect_uri=https%3A%2F%2Flogin.live.com%2Foauth20_desktop.srf&scope=wl.imap+wl.offline_access+wl.emails&client_id=REAL-CLIENT-ID"
self.browser.load(QUrl(url))
Unfortunately, I have no idea how can fix it. Can anyone help me with this?
It's weird but this issue was fixed by adding:
QCoreApplication.setOrganizationName("anOrganizationName")
QCoreApplication.setOrganizationDomain("anOrganizationDomain")
QCoreApplication.setApplicationName("anApplicationName")
Perhaps it would be enough one of these string to fix issue. I didn't check it.
I have a school assignment where I need to use this project: http://web.stanford.edu/class/cs193p/cgi-bin/drupal/system/files/sample_code/Photomania_2.zip
When I first downloaded it, it worked fine. I was working on it one day, when I got this message: "Flickr background download session failed: You do not have permission to access the requested resource."
I didn't know how to fix it, so I went back and downloaded it again to see if I did something to the code that caused that I got that error. When I downloaded a fresh copy of the photomania application, I would yet again get that error.
Does anyone know how to fix this?
Did it stop working on June 27th? The Flickr API went SSL-only on that day. That project probably needs its API endpoints updating to use SSL. I'd ask your tutor about that. Or just try updating all the API endpoints you can find to use the appropriate https: equivalents, as described in that blog post.
I just encountered the same problem. Matt hit the nail on the head. Make sure you add in your API key and do a find/replace to make all "http:" references "https:".