Andy Heinzer Atlassian Team

This is an unfortunate bug that affected JIRA 7.1.7 specifically. Please see JRASERVER-61179 for more details. You should be able to upgrade to any newer version of JIRA in order to resolve this particular problem.

HealthCheck: Free Space has an explanation of this. It tends to appear when the amount of free space is less than twice the current size of the indexes in JIRA. I do not believe there is any way to configure the plugin in this regard. I just noticed that the documentation site appears to be down at the moment, here is a…

Outlook can sometimes not show messages that are still on that mailbox. I would recommend that you try to open that mailbox with a different mail client, such as webmail through a browser, or with a client like Mozilla Thunderbird. Try that first, if the mailbox is empty in the other client as well and you still see this…

JIRA's Application Access page is not intended to control the access level to these other products such as confluence, bamboo, bitbucket, hipchat, etc. You can't control those applications in JIRA like that, but I can understand why you might want to. It is only intended to allow you to control JIRA Core, JIRA Software,…

Changing the address, hostname, or IP should not have any relation to this kind of error. Your log snippet shows that you are getting a SQL exception when JIRA is trying to do a select statement. Yes there is an API call here, but the problem appears to be as to why JIRA cannot make this SQL select statement back to the…

At the moment it is not possible to do that with JIRA Server. JIRA Cloud tends to get these kinds newer features sooner. There is an existing feature request to bring that functionality to the JIRA Server platform over in JRASERVER-63096. I'd recommend watching that case. If this feature ever does make it over to the…

Sorry, I don't see any screenshots in this post. You should be able to create brand new groups with your own selected names and use these throughout JIRA. There should not be any hardcoded group names in JIRA, just defaults. The service-desk-agents group is only created by default when you first install the JIRA Service…

Hi all, it appears that this issue is brought on by a recent update to some JIRA Cloud instances. Introducing the new JIRA experience- explains what this change is. This document does have steps at the bottom that explain how to disable this new look as well. But before you disable this new look.... this guide also has an…

Since you want to arrange the swimlane by epic, your JQL filter will need to find a way to include those epic issues themselves in the JQL results. I think one way to do this would be to adjust your JQL query to look like this: (labels = x AND createdDate >= 2017-01-01) OR issuetype=Epic Doing this should then allow you to…

Within JIRA, you can't actually set the timezone that the system is using. You can only set the timezone default for users, or you can change your personal profile's timezone. By default JIRA is just using the system timezone of the host server it is running on. There is a way to change this without changing the server…

Atlassian does not yet have an official language pack for Dutch in either Cloud or Server offerings for JIRA Service Desk. There are existing open feature requests for these: JSDCLOUD-1630 JSDSERVER-1630 But I found that there is a customer submitted language packs available. From reading Languages - Atlassian Cloud…

I do not believe the JIRA audit log will tell you that information. However you might be able to take a closer look at the $JIRAHOME/log/atlassian-jira.log files in order to determine when that integration might have happened, as well as which user initiated it. Was this a hipchat server or hipchat cloud instance?

You can customize the Resolution Time Report in JIRA. This report uses a saved JQL filter for determining what issues show up here. First you need to create a filter that meets the criteria you need. To do this you will need to go to the issue navigator, Issues -> Search for Issues. From there you need to create a filter,…

JIRA won't send out an automated email to anyone that does not actually have an account in JIRA. That is by design to prevent turning JIRA into an email spamming machine. By default in JIRA, only the reporter (the sender in the from address) would be notified of this issue's creation, along with the issues current…

There is a limit as to the number of projects or issues that can be included in a single plan: JPOSERVER-1671 explains this as 100 projects or 5000 issues to a plan. However I cannot seem to locate any information on just how many plans might be able to exist within a single instance.

I would recommend commenting to that ticket directly: JSWSERVER-14757 There is no guarantee this will be fixed, but explaining why this bug is a problem in your environment might help the development team and product management to increase the visibility of this issue. I would also expect that this issue might be a low…

The project admin role should be able to both see the roles/users for a project as well as add users/groups to different roles. It is possible that you would not be able to search for new users if you were missing the global browse users permission, but even with this missing you should be able to see all the users/groups…

Did you just upgrade when this started happening? Well the JIRA Service Desk 3.0.9 won't be able to work with JIRA 7.4.1, that version is incompatible, you will need to update Service Desk plugin in order for it to work with this newer JIRA version. Most of these errors appear to be plugins failing to startup within the…

I don't think the upgrade would cause this. However there should be at least one user in your organization that has the system-administrator rights. Otherwise no one will have the ability to make system wide changes like that to a user directory. I would be interested to see if you can run the following SQL query against…

The most common cause for this kind of error is that the java trust store JIRA is using does not have the SSL certificate for the site/address it is trying to connect to. The KB Unable to Connect to SSL Services due to PKIX Path Building Failed also explains this error and steps you can take to troubleshoot this.

I was not able to find any plugins in the Atlassian Marketplace that would help direcly with this kind of integration. However searching the Alteryx site I did find some similar requests such as https://community.alteryx.com/t5/Data-Sources/JIRA-Connector/td-p/51562 and…

I'm not sure about using axios, but from looking at other instances with this error such as How to change the mediatype of an attachment via REST API REST API error 415 unsupported media type It seems like this might be a problem with a lack of a content type paramenter. I think you might need to clarify the request by…

I understand that you have an existing Microsoft AD server as a user directory in JIRA and have some concerns about switching user directories. But I am somewhat confused by your questions, as they are not clear to me. If the usernames that exist in JIRA are the same as the usernames in the new AD directory, then what you…

This is a very common error to see when upgrading JIRA. It happens because your JIRA installation still has the old plugin versions that cannot be loaded in the new version of JIRA. But JIRA still tries to load these and you get this error. Details on this are in this KB: Upgrading to JIRA 7 throws a NoSuchMethodError on…

Hi Eduardo, Sorry to hear you are having this error. However the way you described this problem sounds very similar to a known bug in JIRA 7.2.0 through 7.2.5 that could cause this same behavior. Please see JRASERVER-63109 for details. If you are running a version of JIRA in that range, I would strongly recommend that you…

It is possible to do with just the basic JIRA, provided that you don't need to know exactly which person created the issue. JIRA needs to set a value for the reporter when creating issues. The issue collector will allow you to set some specific account to be the reporter of the issue. You could just use this method to have…

In order to have the epic appear on that board, you need to create a JQL query that also includes that epic in the search results. Otherwise the epic will not appear on that board. Since your existing JQL based off the epic link you can't link the epic to itself, so you would need to change the query from: epic link in…

I would try to force JIRA to do a 'lock JIRA and reindex' to see if this helps. Everytime JIRA upgrades there is an expectation that a reindex has to occur. If the indexes in JIRA might have become corrupted, the issues could still be there, but might not be searchable until the indexes are fixed. If they are corrupted,…

The scenario you describe is also explained in the KB: The same sprint is displayed across different scrum boards after moving an issue This is expected to happen when moving issues that are currently assigned to a sprint. Since sprints are not bound to specific projects or boards they can contain issues from any project…

The verification of domains is really only important if you want to enforce a password policy, or use SAML for authentication. If you are not interested in either of these functions, then it isn't required to do this. However if you do verify your domain, it also opens up the ability for you to manage those user accounts.…