Andy Heinzer Atlassian Team

There are different ways to provide this kind of field update via REST. You can either use the update parameter or the fields parameter (just don't try to use both in the same payload for the same field). But when you make use one of these or the other, the syntax can be slightly different. When you use the fields…

Thanks for posting your solution here, Devon. If you want to post it again as an Answer, instead of a reply, we can then accept it as the solution to this problem. In turn that might help other users that might encounter the same problem in the future find this post easier.

Boards are specifically a feature of Jira Software. While you might have upgraded Jira Core here, it doesn't necessarily mean that you also updated the Jira Software plugin here. This will need to happen in order to see that Boards tab in the navigation bar. In Jira 7 and higher versions, you should be able to quickly…

A few questions for you about this: * What version of Jira is this? * What version of MySQL are you using? * What version of the MySQL JDBC database driver are you using? Downloaded from Download Connector/J * What is the specific Atlassian Documentation URL you are using to follow the steps to setup Jira to connect to…

@Pascal Laier That particular plugin is only available in Jira data center. Jira Server can't utilize the functions of this particular plugin at this time. More details on the support of this plugin are in SAML single sign-on for Atlassian Data Center applications.

Thanks for updating the thread with your solution. Would you mind sharing the details of your javascript?

If I could learn more about what version of jira this had been working on, and what version you're using now, it would help me to better understand if this was a change to the API we made between major/minor version changes to Jira. I'm also looking for other ways for myself to recreate this problem so I can better…

Hi Pete, Thanks for the log files, I took a look through these and I found a few things that we probably need to address here. In this specific reply, I'm focusing on the 7.13.1 support zip file you sent: First there are a number of instance of "FAILED PLUGIN REPORT" showing both failed plugins and other plugin artifacts…

Carrie, Unfortunately this specific feature is currently broken. There is a bug about this over in https://jira.atlassian.com/browse/ID-6749 I would recommend watching this for updates. I do expect this to be fixed, at which point the documentation should be correct again. Sorry for the inconvenience. Andy

According to the REST docs on this endpoint https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/version-createVersion a status 403 error code means: Returned if the currently authenticated user does not have permission to edit the version. Which could mean that your request is not authenticated as expected…

The order of your post functions is very important. I think you are probably seeing an example of that here. Check out this related thread: https://community.atlassian.com/t5/Jira-questions/Empty-issue-key/qaq-p/996655 In your case, I think that Jira is firing the status change event in step #1 prematurely. That event…

Jira's APIs are not designed to be able to provide you with an account's password. Check out @[deleted] 's response on a related thread: https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-get-the-logged-in-user-s-password-for-integration-purpose/qaq-p/479853 No there isnt. Passwords are one-way hashed,…

I don't think there is a single REST call you can make to keep up with the data on that board dynamically. As you stated you can call that endpoint by itself, but Kanban boards tend to have a lot more issues matching the main board filter than usually appear there. This is because kanban boards have a subfilter used to…

It looks like this kind of error has been reported before when using the Atlassian-SDK on Windows platforms specifically. Please see the bug report in https://ecosystem.atlassian.net/browse/ATLASSDK-93 In it, other users have reported in the comments there that it might be possible to modify a mvn.bat file in that bin…

Which specific REST API endpoint are you using here? I tried this with a comment endpoint and it seems to work correctly for me in Jira Cloud. curl --request POST \ --url 'https:// example .atlassian.net/rest/api/2/issue/SCRUM-12/comment' \ --header 'Authorization: Basic [REDACTED tokenstring]' \ --header 'Content-Type:…

Hi Sara, Sorry to hear that you have encountered this problem. Changing the context on existing custom fields can be a frustrating process to follow. I saw your comments on the bug ticket as well. You mentioned not having a backup from before this change. I am curious if you are aware that Jira is automatically creating…

There are times when I've recommended using a javascript hack in Jira to hide elements on the page. However in your case, I don't think this is really the best approach given what you told us so far. I understand most of your users only use Jira via the webpage, but technically they are not restricted from making REST API…

You are only one minor version of Jira Core behind where that became possible for Jira Service Desk projects. Please see the details in the Jira Service Desk 3.10.x release notes. It explains how JSD 3.10.x was the first version to introduce this ability to those types of projects. In order to update Service Desk to a…

There are settings that you need to configure both within IIS and within Jira itself for this to work as expected. I would recommend trying to follow the steps in Proxying Atlassian server applications with Microsoft Internet Information Services (IIS). It provides step-by-step instructions on how you can configure this to…

The notification helper is a good utility to use here. As it seems you have already done this, those results are usually spot on in terms of what Jira is configured to notify on. So perhaps there is something else happening here. We do have a KB on troubleshooting notifications that might help here: Email notifications are…

While I'm not an expert in using Perl, since you're using the REST API here, I can say that anytime you create an issue using the POST /rest/api/2/issue endpoint, Jira will provide you a response when that issue is created. It will look something like this: { "id": "10261", "key": "SCRUM-27", "self":…

@Keith Shaw It looks like there was a bug for this in our Identity project tracker: https://jira.atlassian.com/browse/ID-6754 This bug appears to have been fixed at this time. Thanks for the reports everyone. Sorry for the inconvenience.

That is correct. Since the issue was created without a request type, that create issue event has already fired. There really isn't way within Jira to refire that same event after the fact. Since the issue did not have request type set when created, Service Desk can't use it's customer notification system to send out such…

As of today: Technically no. But that said, it's coming. You can sign up for the beta over at https://www.atlassian.com/software/jira/mobile-app/server Cheers, Andy

In regards to using Jira Service Desk which has automation: You don't need to be a system admin in Jira to do this. However you do need to at least be an administrator of that project, and have application access to Jira Service Desk (which consumes a license seat and in turn that user is in the Agent role for Service…

I would recommend creating a support ticket for this over on https://support.atlassian.com/contact/#/ Specifically you should select the option for "Billing, payments, and pricing". By selecting this you can be sure that your request will go to our Customer Advocates team. They can then help you walk through the process of…

That's a very common problem with Service Desk. In order for customers in JSD to get notifications, those issues have to have a request type set. As such when a customer creates an issue they either have to do it via an email, or via the customer portal. Both of those methods set that request type field. However Agents…

A 415 error for that REST call is an unsupported Media Type. It tends to happen because your REST call has defined a Content type that is either incorrect or simply not needed for that specific call. This is also explained in the Fisheye KB: REST API: "Error 415 Unsupported Media Type" I realize that is for a different…

I found a related support case that had a similar error: This usually happens when the access to the IP address/Domain is being blocked on the network. In order to confirm that, if you allow me I would like to ask you the following: * Could you try to test access the same Jira issues from a different network? From your…

Ah, yeah, that is what I was suspecting. Instead of trying to overwrite the default priority icon names like blocker.png, high.png, highest.png, medium.png, low.png, etc, try giving each of your own custom icons their own unique names, like H.png, M.png, and L.png. Basically try using different names to the system…