Andy Heinzer Atlassian Team

There is a way to recover this, please see the documentation https://confluence.atlassian.com/display/JIRA052/Retrieving+the+JIRA+Administrator Please note that the steps for this version of Jira are much different than the current steps for Jira versions 6.2.1 and higher listed in…

Hi @IT ADVITOS This is unfortunately a known bug in Jira. There is a limitation on the length of the database field that stores your LDAP filter. You can read more on this bug in https://jira.atlassian.com/browse/JRASERVER-36979 In short, Jira is only able to store LDAP filters natively that are 256 characters or less.…

Ah, thanks for clarifying Gary, I hadn't considered a mass change to an email domain as being a source cause for this, but yes, that too could cause problems here since Jira is only able to identify email senders based on the content of the message and compare that against the email field in the user account Jira maintains…

This is not the same thing. In Raju's case, he was referring to Jira Server, you clearly are using Jira Cloud (because your site has an atlassian.net domain, we know this is an Atlassian Cloud product). Also Raju's problem is specific to listing which boards appear in a project when clicking on the ellipsis (...) in the…

But because it's based on searching individual's details, it cannot be used when removing data in bulk. The scripts provided in those links I posted can do what you are looking for here. They are not only for removing user details. There are a lot of different SQL update statements in those scripts, because there are lots…

This is a pretty common problem to see. Since the commit data is not appearing in Jira for upwards of 1 hour, I think that this KB will help: Slow Appearing Commits from BitBucket or GitHub in JIRA From that KB: Cause When setting up the DVCS Connection, the OAuth Token provided did not come from an account with high…

Well your scheme parameter in Jira's server.xml should be https not http since that connector is clearly being used to allow traffic in from a proxy using SSL on port 443 to reach the Jira site. If changing that and restarting Jira does not help, please try to recreate the problem and then click into the Response tab in…

Thanks for letting us know. If my answer helped resolve this, please check the checkbox next to my answer to accept it. If there was some other steps taken to fix this, please create a new answer with the details you followed and then accept that answer. Thanks Andy

@Steve Please upgrade Jira to 7.9.2 to resolve this.

On that screenshot page, go to the link called 'Edit Filter Shares'. I know that on that screenshot it shows "No filter shares". However there is a known bug where if you share the filter with the entity called 'Any logged-in user' then that filter is still something any user with a login can see, and in turn the board is…

In this version of Service Desk, the only users that can add public comments to an existing JSD issue are the Assignee (Agent), the reporter, or members added to the request participant fields before the email is processed by Jira Service Desk. As a result, if you forwarded an email with that subject to a new user, and…

Changes were made to Jira between the versions in order to change how users are granted access to Jira and who can see issue data in Jira. There is a bug for this behavior in https://jira.atlassian.com/browse/JRASERVER-45227 Basically I suspect that your account does not currently have access to see the filter that gadget…

Hi @Andriy Dekhtyar _Rozdoum_, We appreciate your contributions to this thread, however I would ask that you please review our guidelines for Marketplace vendors and solution partners. Specifically we want you to identify yourself as being affiliated with this product that you refer to. You can do this either by renaming…

I don't see any problems with the configuration you have in the dbconfig.xml file for Jira. I can see two different approaches to try to resolve this: * abandon the existing database, create a new database, and then import an XML backup of your Jira data into this new empty database * Alternatively, we can try to…

Hi Anu, Atlassian has been taking steps towards making sure that both our hosted services and our server/data center products can be made to comply with the new regulations of the GDPR. I'd recommend checking out this article here on Community:…

I can see a scenario where this would not work. When Jira processes this message, it looks through the headers to figure out a lot of information about that message; such as the sender, the subject, but I think it is looking at the To and CC fields as well in order to make sure that the receipent's email address appears…

Hi Arturo, Sorry those steps did not appear to help. I have created a support case on your behalf in https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-117961 Please see the steps in that case to gather some more information for us so that we can better troubleshoot this problem. Thanks, Andy

It depends. If you're using Jira Core or Jira Software, then the problem with this approach is that every user that emails that address would have to be a licensed user for this to work. In Jira Service Desk, not every user has to be licensed. You can have unlicensed users, these are users in the customer role. They don't…

Hi John, There does not appear to be a way to do this at the moment. However there is an existing feature request to allow an administrator to make this widget appear in a page without the use of the popup. Please see https://jira.atlassian.com/browse/JSDCLOUD-5762 If this was implemented, I would then expect you to have…

Hi Raju, From reviewing this error message, I don't think this has anything to do with Tempo. Please see this KB: Loading Agile Board shows An error occurred Inline Editor That KB explains that this specific error can occur when the inline edit module has been disabled: Cause JIRA Agile's inline edit module had been…

I can't see a way to keep the resolution field required and still correct this. Jira is using that system field in a specific way where any issue that has ANY value at all for a resolution field is being considered resolved. That is the intention of this system field in Jira. As such issues that are resolved will appear on…

I would recommend trying to follow this KB: https://confluence.atlassian.com/jirakb/mysql-communication-link-failure-214338032.html Specifically cause #4. I would be interested to make sure that first the interactive_timeout and the wait_timeout values are for each of these SQL commands: SHOW VARIABLESSHOW SESSION…

Ah, yes that does help. I think what is happening in your environment can also be explained by this KB: https://confluence.atlassian.com/jirakb/unresolved-showing-up-as-a-resolution-for-resolved-issues-163938438.html You mentioned that the Jira Admin had created a resolution called 'unresolved'. I typically only ever see…

Hi Varsha, Business projects are specific to Jira Core. Jira Core did not exist until Jira 7. As such you won't have the option to create a business project in Jira 6.4.x. Instead in Jira 6.4.x, you can choose a project type such as "Project Management" or "Simple issue tracking". These are the closest equivalents in that…

Hi Luu, This is not possible with Jira Server Desk natively at this time. There are existing feature requests for this in * https://jira.atlassian.com/browse/JSDSERVER-4261 * https://jira.atlassian.com/browse/JSDSERVER-1169 I would recommend watching/voting on those issues if this is something you want in Service Desk. In…

I found a few other support cases that showed identical errors. However each of these appears to have a different resolution. These were on the 7.6.0 and 7.6.2 versions where we saw this error, however I have not found a clear existing bug report for this specific version/error. Could you try these SQL queries to and let…

@Jos Helming I believe this issue has been resolved within the last hour. You should now be able to close this banner on the site. I have had at least one other user in Europe who was experiencing this problem before, but has confirmed this is working correctly now. Regards, Andy

Hi Jorge, At this time, the mobile application does not yet have the ability to process Service Desk approvals (a button that would let you accept or decline). However there is a feature request for this in https://jira.atlassian.com/browse/JSDCLOUD-6093 I would recommend voting on this issue and watching this for updates.…

Could you let us know what version of Jira Software you are using here? There was a similar bug documented in https://jira.atlassian.com/browse/JSWSERVER-16513 that was fixed in the 7.6.3 release. Granted that notes a postgres database on the back end, but the message is very similar to your mysql error. If you are using a…

Yes, it is a known bug in that version and 7.8.1, please see https://jira.atlassian.com/browse/JSWSERVER-16509 for more details Please upgrade to 7.9.2 to resolve this.