Ben Kelley Atlassian Team

If you are calling a cloud service, it's good to have a plan for how you will handle API drift. It is certainly a valid plan to do nothing, and this solution has both upsides and downsides. If you are using a 3rd party product that integrates with a cloud service, you want to know that this product also has a plan for…

A suggestion here: If you develop against Atlassian Cloud APIs (including Jira) it is a good idea to subscribe to updates on https://developer.atlassian.com/. While APIs change all the time, breaking changes like this are not common, but they are announced well in advance. This is particularly true if you develop a product…

I suspect the problem is that user names are no longer supported. See https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-user-privacy-api-migration-guide/ There wasn an announcement in October 2018 that user names were being deprecated. You need to specify users using their account ID. You can no longer…

Hi @Nils Rognerud . You can mention users in wiki text using a format like [~accountid:abc-1234-def]. All Jira Cloud APIs support account IDs. Currently if you include a user mention that uses the person's user name in wiki text, it will still render, but as part of user name removal this support is being removed. See this…

Maybe see this post from 2015 https://blog.developer.atlassian.com/discontinuing-ide-connectors-support/

Here it is: https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133

Related: I'm writing up how to generate a client library in the language of your choice from our Open API spec. I'll link it here when it's done. It won't be a drop in replacement for Server's JRJC (as it is not auto-generated), but it might be useful in terms of how you respond to future API changes.

@dt0b35 sorry but we don't ship client libraries. You can generate your own from our Open API spec though. I will write up a page on that. (I found that swagger-codegen didn't like a few things, but the work arounds were fairly straightforward.)

Jira Cloud customers could create a feature request ticket through the normal support process to ask that a similar client library for Cloud is published. Cloud and Serve APIs differ in many ways, so I imagine the libraries would always be different. Another route would be to generate REST client code from the Open API…

Again, while I am not involved in the development of the client library for Jira Server, I think it might be more confusing if the official Jira Server library had this change. The published documentation for Jira Server developers is that version X of the library works with version X of Jira Server. There are many…

While I can't comment on that PR, my feeling is that given this library is for Jira Server, this patch would make it incompatible with Jira Server. There are a number of differences between Server and Cloud APIs.

It is probably worth keeping in mind that there are a number of ways that Jira Server REST APIs (especially from an older release like 5.1) are incompatible with Jira Cloud REST APIs.

I understand. Although there are often small changes and new features for Jira Cloud APIs that the Jira Server library didn't support, possibly that wasn't a problem for some people. These changes by their nature were breaking changes though. It wasn't a decision we took lightly, so we sought to give as much notice as…

Please note the section under "Compatibility with Jira" for JRJC on https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview The Jira REST Java Client works with Jira Server, but not with Jira Cloud.

Hi @Sri Kumar Note that this change is only about how Jira Cloud treats user mentions in wiki text, and doesn't affect ownership of anything. The editor in Jira Cloud has created user mentions referring to account IDs in wiki text for some time now. For customers wanting to import this data in Jira Server, there is a…

I think it is because you are sending the wrong MIME type with "dataType: 'json'". This article discusses the issue: https://stackoverflow.com/questions/24528211/chrome-refuses-to-execute-an-ajax-script-due-to-wrong-mime-type

Another way might be to move those issues out into a different project.

If you can configure another email client to use IMAP to read email from Office 365, then the settings should be similar. The email channel will try to log in to IMAP as you, and see if there are any unread messages in your inbox. That error message sounds like it connected, but couldn't log in. Another thing to check is…

If you have Jira Service Desk you can do this with an SLA. https://confluence.atlassian.com/servicedeskcloud/setting-up-slas-732528967.html

Do you have IMAP enabled for your user from the Office 365 side? If you can connect to your account using IMAP, then the settings should be the same in Jira.

Is a "location" a physical location, or a different company? (or both?) One option is to add a field to your request form to ask the customer to specify the location. Are you using Service Desk in cloud? If you want to be able to automatically sort tickets by customers' companies, you could set up an organisations in your…

When you edit the dashboard (logged in as you), does it show "Shared with public" next to Shares? When you choose the group to share with (the field under this) you need to click the "Add" button to the right, then click Update.

When I have seen this before it was generally to do with how the browser handles intra-page anchors, where the anchor text contains certain characters. e.g. If you have a section heading called "Overview", it will generally work well in all browsers. If you have a section heading called "Questions?" the "?" will make it…