DPKJ Community Champion

After installing JDK (and not JRE), try adding this, export JAVA_HOME=`/usr/libexec/java_home` in your /Users/<your_name>/.bash_profile file (create it if it doesn't exists) Once this is done, either close terminal and open it again, or you can use `source` command. source ~/.bash_profile Also after this test if JAVA_HOME…

@Graemethis is a good move. Things you need to consider are, * Before you do this,* Get trial license of confluence cloud and get feel for it, * Make sure all plugins (if any) you use are available for cloud * Some part of UI is different on cloud get used to it * You have to upload your content to cloud yourself,…

@Niveditha * User installed add-ons,* They are kept inside Jira Home directory, Have you changed it? * Some add-ons have different compatible version for Jira 7 and Jira 8, you will install them again after update. * You can install service desk by searching inside UPM in Jira itself, you don't need to upload it.

No it will not ask for any information. Updating add-ons is simple UI operation in Jira. But I suggest you renew licenses before updating any add-on, because some add-ons might not work properly after upgrade if you don't have valid license.

No, you can not find that information about add-on. At most you can look at each module and screenshot they provide and do the guess work.

@饶青There is no development in limiting amount of information we get per issue field as of Jira 8.

It means, machine where Jira is hosted you need rights to make changes in Jira installation directory.

Go though this article - https://confluence.atlassian.com/adminjiraserver/running-jira-applications-over-ssl-or-https-938847764.html You need an admin access to machine where Jira is hosted, and if you are buying certificate from external authority you also need an access to domain provider.

@Fahad Siddiquiyou need specify your need before I can give you clear guidelines, Are you trying to create certificate for your Jira, and if yes do you have any proxy server etc?

I think getting a new certificate is better choice. I am not aware of "production link".

I personally use this library and it works fine all the time. kong.github.io/unirest-java This is really simple to use. Code looks like this, HttpResponse response = Unirest.get("{jira_url}/rest/api/2/issue/{issueIdOrKey}") .header("Accept", "application/json") .basicAuth("{user_name}", "{password}")…

If you are not aware of how certificate was created, you have two options, * Click on lock icon on browser's address bar after opening site for which you want to verify certificate and look at certificate information. * Completely ignore the old certificate and get a new one, it will not effect anything. For example -…

When you want to move page from one space to another, you need to have "Add Page" permission on target space please check this and verify. Site-admins are not always granted this permission, but you can configure it.

@Fahad Siddiquirenewal of certificate depend upon your certificate issuer. For example, If your certificate is self signed (using openssl/keytool etc), it is as simple as generating a new certificate. If your certificate is issued by Amazon for AWS service, you can setup auto renewal. If your certificate is issued by Let's…

There is no accountId field on Jira Server and Data Center (i.e. on premise install). Field that you need to use in username.

@Amir Katz (Outseer) This page takes you to latest page always - https://developer.atlassian.com/server/jira/platform/rest-apis/ Other then this, if you want to view API of specific version, edit version information in this url - https://docs.atlassian.com/software/jira/docs/api/REST/<VERSION_NUMBER>/ This is what I use.

You don't need to change anything in your Jar, just when you upload new version on marketplace you can set compatibility. Something like this appear on Marketplace -

Here you go, I was on this page only - https://docs.atlassian.com/software/jira/docs/api/REST/8.3.3/

When you release plugins to Marketplace, you can set compatibility of one version till Jira 7 and for other version Jira 8.x onward. This way when someone has Jira 7 version installed and upgrade to Jira 8, without updating your plugin, UPM will tell admins to upgrade your plugin, and they also will incompatible…

@Fahad SiddiquiI can only give few suggestions here, * If user belong Active Directory check his settings, * verify if issue occur when user try to access using different machine and browser. * Try resetting user's password etc. I hope this helps you.

@winter wongNo project version table also doesn't contain any information like this.

"Epic Link" = <EPIC_ISSUE_KEY> AND issuetype = Story This will list all stories in an epic. If you want to see more than story remove `issuetype` filter.

You need to set this up in your account preferences, visit this page to do this - https://my.atlassian.com/email

I don't think this is possible programmatically.

Can you share bit of logs. Also have you checked Jira Home and Proxy settings (if any).

This is tough information to gather. This can be obtained from DB and API, but I am not sure though I suggest you create a separate question for this.

This is fairly straight forward, * Backup everything * Copy your Jira Installation, Jira home to new server. * Install Java and Database on new server * Dump database on old server and upload this dump to new server * If your home path have change from old server to new server, update home path in…

By programmatically if you mean inside your plugin, you can this class https://docs.atlassian.com/software/jira/docs/api/8.0.0/com/atlassian/jira/util/BuildUtilsInfo.html Usage is fairly straight forward, String version = buildUtilsInfo.getVersion(); //something like to check versions.

Sure, I am happy to help. List down your expectation from Requirement Management Tool and establish matrix for each strategy. This way it will be easier for you to foresee problems you might face in each strategy.

Oh! everything you are using is almost new, you can easily migrate and then upgrade to latest Jira. DB and Java version will not be needed.