Hi,
I just wanted to update one of my old scripts that is using JRJC in order to prepare it for the upcoming major changes to Jira Cloud REST APIs and noticed that the newest version is still not supporting accountId fields out-of-the-box. Have I missed anything?
Are there any plans to add accountIds support to JRJC by 29 March 2019?
Regards,
Jakub.
That project does have activity on it. And there is an existing feature request for the accountid support over in https://ecosystem.atlassian.net/browse/JRJC-240
However this specific issue has not been assigned. This particular project was an Atlassian Labs creation. About Atlassian Labs:
Experiments released into the world! Atlassian Labs holds unsupported apps and personal projects by Atlassian developers. Although you may find unique and highly useful functionality in the Atlassian Labs apps, Atlassian takes no responsibility for your use of these apps. The apps are often developed in conjunction with Atlassian hack-a-thons and ShipIt days and are provided to you completely “as-is”, with all bugs and errors, and are not supported by Atlassian.
This project is technically unsupported per the marketplace listing. Which means that there is no clear timeframe on if or when such an update might come to this project. It is possible, but it is not guaranteed. I would recommend watching and voting on that request ticket if this is something you rely upon. I can certainly see how this would be useful. If this is something that will come to this project, I would expect that feature request ticket to have an update on it detailing the version that might offer this ability.
Thank you @Andy Heinzer ,
I already implemented accountId support by myself. What are the chances that the team will accept pr?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not seeing a pull request against that repo. Could you provide me the link to where you made this pull request? I'm not sure of exactly who would have to review this request, but I will ask around.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andy HeinzerI haven't made that pull request yet, just wondered if anyone is looking at them.
I will try to find some time by the next few days to create this pull request. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andy HeinzerI cloned the latest JRJC and built it locally, so I am ready to prepare the patch. However, is there any permission needed to create a pull request against https://bitbucket.org/atlassian/jira-rest-java-client ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have to admit, I am not well versed in the use of bitbucket or git, so forgive me as I don't always know the details here. But I did find more info in the readme for this project that I hope will help here. From the https://bitbucket.org/atlassian/jira-rest-java-client/src/master/README
Please see project documentation at https://ecosystem.atlassian.net/wiki/display/JRJC/.
In order to start JIRA please execute atlas-debug from test directory.
If you want contribute to project feel free to send pull request (preferably with tests ;)).
IMPORTANT: please do not touch the rest_api_guard branch - master is being auto-merged to that branch so there is no need to do any changes there (doing so will cause conflicts).
To run a single test class, you can pass -Dit.test=ExamplesTest to maven.
In order to run integration tests on a snapshot cloud version of JIRA run:
mvn clean integration-test -Djira.version=1001.0.0-SNAPSHOT -Pjira-cloud -nsu
To run integrations tests manually, you need to set up JIRA with a running instance of postgres.
To start a pre-setup postgres run
docker run -p 5434:5432 docker.atl-paas.net/jira-cloud/postgres-ci:9.5
and then in another terminal
mvn jira:debug -Ddocker.host.address=<Docker-machine Ip> -Ddatabase.port=5434
you can find your docker machine ip when running docker quickstart.
This makes it look like you can do a pull request, but that they would prefer you run some tests against your changes. I'm sure that other users will want to review your code before it would be committed or merged.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pull request created: https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andy Heinzer who owns the jira-rest-java-client plugin? Looks like @Jakub Sławiński filed a pull request 1 year ago, but no one has merged it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Craig Rodrigues Thanks for the heads up here. I'm not sure who exactly owns this repo, but I was able to reach out to some follow Atlassians about this problem. It looks like this change has now been merged into the master branch.
Apologies for the great delay here, and thanks again for asking about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am glad I could help. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.