Ben Kelley Atlassian Team

The documentation for the specific version of Jira Server you have does talk about which major/minor versions the different client APIs support. I get that if you just grab the jar from a repo it doesn't link back to the docs describing what that jar is for. I understand that if you only use one API, it would be convenient…

Hey @Bill Bill . I guess one of the things about cloud is that there are small changes all the time. Any published client for cloud would be out of date almost immediately. The jar file you are looking at is probably for Jira Server. For Jira Server, you installed a particular version of Jira on your system, and so you can…

Note that the FieldValueClause problem should be fixed.

I'm not quite sure what you mean by labels. Sometimes turning on debug can be helpful to see what data is coming back, so you can check if the thing you are looking for is actually returned in the response. e.g. configuration = ApiConfiguration() configuration.username = 'my@email.com' configuration.password = 'mypassword'…

Hmm __hasattr is part of the library code that swagger-codegen writes for you. It should be near the bottom of api_client.py.

Hi @Oi Lee . That looks like this bug in swagger-codegen: https://github.com/swagger-api/swagger-codegen/issues/10129 I encountered the same error, and so I submitted a fix for this. It looks like the latest version of swagger-codegen came out in late June, but the fix for that bug didn't go in until July. Sorry about that…

In this article I go over generating a Jira Python client from the Open API spec. The code it generates includes the correct requirements.txt to pull in the required libraries. https://community.atlassian.com/t5/Jira-articles/Generating-a-Python-REST-Client-for-Jira-Cloud/ba-p/1747050

Hi @Benjamin C. John . Check out the Confluence Open API spec. I made some fixes. I'll publish a separate blog post about it.

Hi @Thomas C Buell . Make sure you read my follow up post where some of the problems I mention here are fixed (my first comment on this page). Yes there are Maven dependencies. They are slightly different depending on which "library" option you choose for Java. By default the Java generation creates a self contained…

Hi @Benjamin C. John . I did raise this with the Confluence team. They are taking a look at it.

Another way to do this is to define the JQL for a board to include appropriate tickets from both projects. As your view of the project is often the board, this might do what you want.

Note that you're using the Swagger spec for Jira Cloud, but you tagged this as Jira Server. The Cloud and Server APIs have differences.

See also: https://github.com/swagger-api/swagger-codegen/issues/11011

So it's how swagger-codegen maps the enum value to a type name. I can't see an easy way to specify that you need to send "xyz" but it should call it "abc". Looking at how enums work in Open API, I don't think there's an easy way to get around how swagger-codegen creates identifiers for Java. I might submit a bug report for…

The IssueTypeIDs problem should be fixed now. I see what you mean about the FieldValueClause. I'll look into it, and comment back here.

@Eric Johansson could you perhaps give some more details in a new thread/question?

Hi @Matteo De Franceschi . It might be better to ask that in a new thread, but for Connect where you have AtlassianHostRestClients, and you are using the resttemplate flavour from swagger-codegen, you can construct an ApiClient from a RestTemplate, so like: String baseUrl = "http://mysite.atlassian.net/";…

Hi @Neeraj . I was working with Spring's REST template today, and I saw the issue you mentioned about Component. I have renamed Component to ProjectComponent as you suggested. This should be reflected in our spec in the next couple of days. Thanks for your feedback!

Hi @Andreas Schröck . Maybe it's worth asking about that in a new thread/question. Things like which resource you're accessing (e.g. is it for Jira Software or Jira Service Management/JSD?) and what HTTP client and language you're using might help to understand what's happening.

I found that you need to then get the project, and set expand to be "issues". e.g. ApiClient apiClient = new ApiClient(); ProjectsApi projectsApi = new ProjectsApi(apiClient); ProjectIdentifiers identifiers = projectsApi.createProject(projectInputBean); Project project…

Hi Neeraj. The IssueTypeIDs/IssueTypeIds problem should be resolved now.

We fixed some of the problems I described above. See the follow-up blog post here: https://www.atlassian.com/blog/developer/update-to-jira-clouds-swagger-openapi-docs (updated link - November 2024)

Sorry I'm not clear if this is a question about scriptrunner, or a question about Jira REST APIs. Is "using properties" to do with scriptrunner?

I wonder if you could describe what you are trying to do in a bit more detail.

It looks like the ability to manipulate screens (and screen schemes) is in progress (but not currently available). This Trello board might be helpful: https://trello.com/b/8XBuIeIu/atlassian-platform-for-developers-roadmap

Hi. Account ID is a Jira Cloud thing. Jira Server doesn't have account ID.

Hi @Jason Fingerhut . The ability to search for users and mention them in a ticket definitely behaves quite differently between Server and Cloud. There are certainly limits on the visibility of requests in JSD. Unfortunately the fuller workings of who does and does not appear in the user picker is beyond my scope. I would…

Hi @Jason Fingerhut . That issue seems to be for JSD Server. This change only affects JSD Cloud.

Hi @[deleted] . For the moment no, as until we remove support for user names, that would be ambiguous. I guess it is something we can consider for the future though.

You can create a mention from your integration using the format [~accountid:abcde-12345] where abcde-12345 is the account ID of the user you are mentioning.