Andy Heinzer Atlassian Team

It is strange to see that your workflow is also setting the assignee to the value of the reporter. That part should not usually be possible in a service desk project since only Agents are able to be set at the assignee of issues in a service desk project. That is not common to see, so perhaps that post-function is a factor…

Hi @SENTHIL KUMAR CHANDRAHASAN I am afraid I never got a response from Gopi about this issue. Usually this problem happens because a system plugin is unable to start up. But what causes that can vary. Typically I would recommend these steps: * Stop Jira * Go into $JIRAHOME/plugins/installed-plugins/ * move the contents of…

Hi Freddy, I understand that you are not able to transition an issue into another status using a particular scrum board. Could you share with us the filter being used for this board? I ask because if your filter is selecting issues from multiple projects and/or multiple issues types it is very likely that some issues will…

The Community site should be using the https://id.atlassian.com site record for your account name, email address, etc. However this does not sync immediately, like other Atlassian sites can. Instead this only happens when you login to Community. So I would recommend the following steps: * Go to…

Hi @Vasilis Gennaris It appears that this is a bug in that particular chart. We are tracking this defect in https://jira.atlassian.com/browse/JRACLOUD-67143 please watch this issue and vote on this to help our development team prioritize fixes like this one. The Workload pie chart is specifically set to report on one of…

This survey is not sent out based on the issue's status, but rather when the issue gains a value in the resolution field. How is the resolution being set for issues in this workflow? Is the resolution selected via a transition screen? OR is the resolution set via a post-function in the workflow? You can use either of these…

Hi Brad, I'm not familiar with using Go myself to make API REST calls, however from searching on this topic I came across this post I thought might help: Don’t use Go’s default HTTP client (in production) In it, Nathan explains a scenario in which these kinds of Go rest calls can get stuck in a TLS handshake because by…

Awesome, thanks for sharing your solution here @Yusuf Tran As for your question about Atlassian adding such a header in the future: I don't have an expectation that Atlassian would explicitly do this for a proxy configuration. As you have seen, sometimes implementing higher security features can cause applications to not…

Hi Jason, You could use the changelog to try to try to figure this out, but I imagine that is a lot more data to go through to find this information. However off hand, the Burndown Chart/report comes to mind as a good means to track issues that were added or removed to a started sprint. When you add or remove an issue to…

Hi @Jean-François FORGET I am afraid that the REST API endpoint that performs transitions, POST /rest/api/2/issue/{issueIdOrKey}/transitions is not actually expected to provide any other REST response other than the HTTP 204 code for a successful transition. From that page: Responses * STATUS 400If there is no transition…

Looks like you have narrowed the problem to the network configuration. It sounds like you have two layers in front of Jira here, so I'm not sure that there needs to be another configuration change yet. It's very strange that this works correctly in Chrome, but not firefox. I would be interested to see if we can learn more…

Your dbconfig.xml looks ok to me. I don't yet have an explanation as to why you might not be able to connect with those settings, perhaps there is something wrong with the URL value, or the username/password in question. I would recommend using the sample dbconfig shown at the bottom of this document:…

Try this * Stop Jira * go to $JIRAHOME/plugins/installed-plugins/ * Move all the files in this folder to a temp folder outside the Jira home directory * In the Jira database, let's clear any flags that might be preventing system plugins from starting up as expected, run the SQL commandtruncate table pluginstate; * start…

Hi @[deleted], Users like autonomatt have Starter licenses. As such these users cannot create support requests directly to Atlassian select or priority support. Instead for these users, when they visit the https://support.atlassian.com site, their requests are just being posted here to Community again. So it's probably not…

Hi @autonomatt * What version of Jira is this? * What version of Agile/Software are you using? * Could you share with me the details about your Agile license? I would be interested to learn what your specific Agile license key is, I can obscure that data in the post later on.

Hi @Rachid Amajoud I created a support request on your behalf, please see https://getsupport.atlassian.com/servicedesk/customer/portal/3/SDS-33738 for more details.

@webncut From reading your stacktrace, it is not clear to me which table is trying to be updated here. So I believe we're going to need to see more complete logs to better help here. Unfortunately, our Community site does not yet allow for uploading of such binary files. So I created a support case for you here where we…

What version of Greenhopper are you using? I did come across a request to publish the old greenhopper rest api reference guides in https://jira.atlassian.com/browse/JSWSERVER-13299 It does not appear that Atlassian has any of these documented at this time. However the greenhopper product has been deprecated for some time…

Hi Yusuf, Since you're using 7.9.2, the fix for that bug report is already contained in that code base of Jira. When this happens in your instance do your Jira logs have an entry like this found in the bug ticket JRASERVER-64095? 2017-02-14 15:57:28,689 http-nio-8080-exec-202 ERROR anonymous 6x15350x1 oclbhd…

Hi Pedro, If this was something you could fix in the translation yourself, then you could do so by going to our site https://translations.atlassian.com then locating the language and key, and in turn offering an alternative translation. However from my investigation into this, I was not able to find this particular string…

Hi John, You can't update Jira Core directly in the web interface of Jira. Instead you will need to stop Jira, and then run through one of the upgrade methods explained in Upgrading Jira applications. For these upgrades on a Linux environment, you are going to need to select the .bin/Linux executable, or one of the archive…

I don't know if you have actually had a prior service desk install here or not. If you did not, then you don't need to downgrade. So we can try to continue getting this version to work, but if it turns out you had an older service desk here at some time in the past, we will need to address that old data at some point. In…

Just to circle back to this thread, we found the following steps were taking to help resolve this problem: * Stop Jira * Move all the files out of the <jira-home>/plugins/installed-plugins/ directory into a temp directory outside the <jira-home> * In the SQL database that Jira is using, please clear the table that tracks…

I'm afraid our community site does not allow for the upload of non-images at this time. However you could use a service like Google Drive, Dropbox, etc in order to share that file to a public url, and then post that url to this thread so we can take a closer look.

If you had Jira Service Desk on an older version, such as 2.5.x back with Jira 6.4, then there is a problem here. Your Jira database likely contains old database records from this previous service desk installation. The only way to upgrade those old records is to first install a Jira Service Desk version between 3.0.0 and…

The last log entry from that zip file appears to have been from last month. 2018-05-04 12:18:13,563 localhost-startStop-2 INFO [c.a.jira.startup.DefaultJiraLauncher] JIRA launchers stopped in 32542ms However from reviewing the rest of the logs, I can't see a clear problem with your instance. It just looks like Jira has not…

* What version of Jira did you upgrade from? * Did you have Service Desk installed at any time for this previous Jira version(s)? I understand you installed Core to 7.10.1, but if you had Service Desk on an earlier version, it is possible that you cannot upgrade directly to the latest version in order to upgrade that data.…

Thanks @Axel Joester That is something I did not think about here. Jira does not yet support the 8.0 version of mysql or its 8.0 jdbc driver. You can use the direct link to download the latest 5.1.x version instead https://dev.mysql.com/downloads/connector/j/5.1.html

For Server, you'll instead want to review the server doc about Licensing and application access. The developer role on a service desk project is expected to be for Jira Core or Jira Software users that can collaborate on Service Desk issues. However in order to respond to customer requests in a Service Desk project, users…

You could use the startup option called -Djira.downgrade.allowed=true If this is set in the Settings properties and options on startup, then Jira will attempt to downgrade your version. That said, I don't usually recommend this option. Atlassian provides supports for upgrades. However Atlassian does not explicitly support…