Ben Kelley Atlassian Team

1 - I wish, but probably no. 2 - interested to hear what apps people are building for Forge, and how AI is speeding up their workflow

According to the docs https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-groups/#api-rest-api-3-group-member-get the scopes you need for this endpoint are: read:group:jira read:user:jira read:avatar:jira You only have read:group:jira.

I have asked a developer to take a look at this. I suspect the spec is slightly incorrect in trying to specify an array of enums. It parses OK with swagger codegen, but not with openapi generator. If this is blocking you, probably the way forward is to create a support request about this particular problem.

The instructions here are definitely outdated! A lot has changed in 4 years, including improvements to consumability of our spec. See one of my early comments on this article, linking to a new article. There should be no need to make any edits to the spec any more. I was building using swagger-codegen-maven-plugin 3.0.63…

Hi @Gaetano Manzo I had a quick look at this. I don't have openapi-generator configured, but I did build with the latest swagger-codegen (3.0.63). It expresses this as: public enum ExcludeEnum { ASSIGNEE("assignee"), REPORTER("reporter"); // ... } and in ApprovalConfiguration it has a list of the enums: private…

As mentioned by @Chandim Chatterjee this seems to be a known bug in swagger-codegen. https://github.com/swagger-api/swagger-codegen/issues/10196 I guess the solution for now is to use openapi-generator if this bug affects you, or else wait for the fix for swagger-codegen to be released.

Great find @Chandim Chatterjee . I agree - it's probably the swagger-codegen bug you linked. There's a comment there that openapi-generator works OK, or else I guess you could wait for the bug fix.

@Chandim Chatterjee how did you generate the source for your client? (e.g. which version of swagger-codegen, and did you use the latest published swagger spec) Can you confirm you're requesting this from a Jira Cloud site (and not Server or Data Centre)? (FWIW I can't see the original stack trace any more, so I can't see…

Hi @jon martin solaas. Thanks for the comment about openapi-generator. We made a few fixes to the spec since this article was originally published, so hopefully none of the hacks are needed any more! Thanks for the tip on date/time formatting.

Pour les nouveaux tickets, le statut est « TO DO ». C'est pourquoi il affiche le nombre de jours depuis la création du ticket. Vous pouvez modifier la définition des colonnes. Dans mon équipe, la première colonne affiche uniquement les tickets sélectionnés pour le sprint en cours. Nous utilisons un statut comme « prêt pour…

Lorsque vous créez le ticket, il commence dans la colonne "to do". C'est pourquoi il indique le nombre de jours depuis la création du ticket.

Depending on where you are seeing the issues you can change the sort order. Sorting by creation time or by issue ID should get you what you need.

My apologies for replying in English. The number of points correspond to the total time in that column. If you drag the ticket to a new column, and then drag it back, it will remember the total time in the original column. Does this describe the behavior you are seeing?

I'm guessing this question is about user management, where someone has configured that they manage all users with a particular email domain. Does that sound correct? As described in https://www.atlassian.com/software/access/guide/organizations-domain-claim It is still possible to create multiple Jira instances, and invite…

This is a Java API for Jira Server for writing Java plugins, where you install the plugin in your Jira Server/Data Centre instance. This is very different to the REST API.

Ah this is a tricky one. The mapping between an email address and a unique Atlassian account is 1:1. That's why you get that error message. Essentially now you have 2 accounts, one with your old email address, and one with your new one. It's telling you that you can't use that new email address, because that belongs to…

Hi there. Good question! No Atlassian does not publish a pre-built library to call Jira Cloud APIs. The Maven artifact you list is the Jira Server library. The Jira Server library is built to work with a specific version of Jira Server. You will find that many things are different in Jira Cloud. There is a solution though!…

If you follow the prompts to set up the custom email account with Jira, it will ask you for credentials to log in to that email account. Jira then periodically logs in to that account (using the credentials you supplied) to check if there are any new messages in the inbox. That is, it doesn't rely on your email provider…

The Jira Server REST client that you're using is not designed to work with Jira Cloud. It's good that it previously worked for you, but I can't really suggest a fix for this problem in terms of the Jira Server REST client code. New versions of the Jira Server client ship that match the released versions of Jira Server/DC.…

It's a bit hard to tell what is happening. It sounds like you're saying that you have been using the Jira Server REST client successfully against Jira Cloud (even though the APIs are in general not compatible). I'm not quite clear which Cloud API the above code calls (and hence where the new enum type is appearing).

Note that the above linked page https://docs.atlassian.com/jira-rest-java-client-parent/5.0.2/ refers to the REST Client for Jira Server version 5.0.2. Just checking if you're trying to talk to a Jira Cloud or Jira Server instance (as this question is tagged with jira-cloud). The APIs are different between Server and Cloud.

Note that we updated the Open API/Swagger spec since the original "Generating a REST Client for Jira Cloud" to make it easier to use with code generators. See https://blog.developer.atlassian.com/update-to-jira-clouds-swagger-openapi-docs/ The main difference between versions 2 and 3 is that version 3 uses Atlassian…

OK sorry I don't have an immediate answer for you. As an unsupported product we can't really give you a timeline, but I will take a look at this at some stage.

Hi yes I know about Sticker Printer For Jira. I just tested it now on a trial Jira instance, and I was able to install it OK.

I get quite different code for the same config/command. I only see this method signature in client/JSON.java: public static GsonBuilder createGson() But the method I get looks like: public static GsonBuilder createGson() { GsonFireBuilder fireBuilder = new GsonFireBuilder() ; return fireBuilder.createGsonBuilder(); } I'm…

@Pooja Varde are you working with Jira Cloud? I wouldn't expect this to work with cloud. "/rest/api/2/user/search?username="

Perhaps you could indicate what options you used to to generate your library, and give some sample code you are calling that is failing.

Also, it looks like you are running a test that is failing. I don't think you can run the generated tests without modification.

I'll reply in https://community.atlassian.com/t5/Jira-questions/Getting-error-while-using-jira-cloud-api-from-swagger/qaq-p/1911243

What URL/API are you accessing? It's hard to get any context here.