Andy Heinzer Atlassian Team

When you setup a proxy in front of Jira, there are steps you need to take both to Jira's configuration and the proxy's configuration in order to make sure that this connection works as expected. As a general outline, I'd recommend trying to walk through the guide Proxying Atlassian server applications with Apache HTTP…

Hi Jeff, Is the bug you are referring to https://jira.atlassian.com/browse/CONFCLOUD-62589 ? I took a closer look at this issue and it appears this issue was initially prioritized below what we would expect in our Bug fixing policy. That particular bug has had its priority raised from Low to High just in the last hour. So…

Hi Jan-Philip, From looking at your log I found this error: 2018-10-04 19:25:54,741 http-nio-8080-exec-20 ERROR anonymous 1165x11x1 1nzwwqt fe80:0:0:0:619a:d24d:122b:9625%2 /secure/SetupDatabase.jspa [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following: CREATE TABLE cwd_application_address…

I'm not sure I understand what you are asking here. Is the concern that all the issues in a project have a historical edit showing from Jesse at exactly 11:49am? Or is the concern that all the issues show Jesse to have had this edit immediately after the user created it? If is the prior, I would suspect he was using the…

What tends to happen in cases like this is that your old setup has Jira connected to a specific IP/Address for Crowd in order to handle all the authentication. And since that address is likely changing due to this migration, the settings that handle this in Jira need to be updated to let these users login. For this reason,…

This just confirms my suspicion that the source of the problem here is that the two different Jira installations are using different character encodings. I suppose it might be possible for you to get around this problem by trying to manipulate the csv file using a replace function to try to change all the line breaks with…

It looks like the UPM might be stuck trying to update itself. I would not recommend trying to manually edit the database to try to resolve this, instead what I would recommend would be to * Stop Jira * Go to your $JIRA_HOME/plugins/installed-plugins/ folder * Remove all the 'universal_plugin_manager', 'upm', 'self-update'…

Service Desk has additional requirements in regards to which users can work issues. For example, in a service desk project, in order to transition the issue, the user making that transition call has to be licensed as an Agent. This is explained in more detail in Setting up service desk users. I suspect that you might see…

Ok, I understand you have a security level called View, that only allows the current assignee and reporter to view the issue. However if your test users can still see issues where they are neither of these roles it means that these specific Jira issues don't have this security level set on them. By default, issues in Jira…

I believe the problem here is your version of Java: java.vm.version=10.0.2+13 Which appears to be a Java 10 distro. The problem with that is the SDK currently only supports the Java JDK 8 versions as per https://developer.atlassian.com/server/framework/atlassian-sdk/downloads/ Perhaps you already have this Java JDK 8…

I should preface this response with the fact that I have not used this plugin and I don't know how it works. That said, the approach I would take here, since you're using Jira Server, would be first login to Jira as an admin, and then navigate to the Gear Icon -> System -> Plugin Data Storage. Or navigate directly to…

The permissions scheme will need to be setup to allow these users to view these issues first. It sounds like you have that part setup correctly if they can see all of these. The ability to restrict specific issues in a project like this is handled by issue level security. Not only will you need to define at least one…

It's been a lifetime since I used this, but back in my Windows administration days, I used a Microsoft utility called Orca in order to edit MSI files. I had varying levels of success in regards to creating usable MST (transforms for MSI files). I recall being able to apply these mst files along with the msi files that I…

The sprint report is taking a snapshot of the issues and their statuses at that time. To try to recreate this via JQL is a bit different, because issues can still change status and even been added/removed after the sprint is actually completed. However since JQL does track historical changes to some system fields like…

Encapsulating the data within " " should work to preserve this line break information for that field. However that does not appear to be the case for you here, I suspect that your source Jira instance might not be using the expected character encoding that Jira expects (UTF-8). In turn, even if your destination instance is…

Hi Anders, From the link you posted, the screenshot I think you are referring is not the card itself, but rather the new issue detail view that appear when you click on a card. In which case there is not currently a way to customize the fields that appear on this view. There is an existing feature request to be able to do…

I dug into the source code of Jira to find the ObsoleteRowRemover.java and found this comment in the file to explain its function: /** * Removes the obsolete row based on updated column. If for a unique combination of issue id and provider key, there are * multiple rows, it removes the older one and returns the latest one.…

Not really, it just means that there is a certain set of libraries used for creating sample projects (projects with some basic issues and generic descriptions, etc), and without the welcome plugin in that version, you couldn't use that specific functionality in Jira.

It depends on how you make this switch. If you add an additional user directory in Jira to this LDAP system, and that user directory has the exact same usernames that Jira has for your user accounts, and then you order this new user directory above the Jira internal user directory, then your end users won't have to create…

These files exist in the $JIRAINSTALL directory. Any file in that path can be altered by an upgrade.

In this case, I think you are looking for a specific version name/number, namely the unreleased ones in that project. As such you can retrieve this by using the endpoint of GET /rest/api/3/project/{projectIdOrKey}/version More details on the syntax of this can be found in Get project versions paginated. This endpoint will…

The history tab of an issue actually is displaying the user accounts 'userkey', and not the current username. If the account has never been renamed, then the userkey will match the username. However that userkey value is always expected to always be the same once the account is created. There technically is not yet a…

The problem here is that your syntax isn't actually looking back -1 month, but rather -1 minute. The 'm' in JQL is in reference to minutes, not months. But within those startOfMonths functions, you don't need the m at all. Instead try using just status changed to "Dev Complete" AFTER startOfMonth(-1) BEFORE endOfMonth(-1)…

Hi Curtis, I believe the problem you are seeing here is a known bug in this specific version of Jira. Please see https://jira.atlassian.com/browse/JRASERVER-67974 for more details. This problem appears to be happening because this version of Jira included an updated version of Apache's Tomcat that has some slightly…

In your case, it seems clear you are having a SQL exception during the setup. This would tend to indicate that the database is not setup correctly, or is not supported by Jira possibly. From your error it looks like you're using mysql. Is that correct? What version of Jira are you using? What version of MySQL are you…

Are the dates showing in Jira off by exactly 1 day from the dates that you entered? If so, then I suspect that the problem here is that your user profile is using a timezone that is different from the timezone that the Jira application is using. And that you are likely 1 or more hours ahead of the Jira system timezone.…

I would recommend starting by checking out the Jira Sizing Guide, this can be helpful to understand what kind of resources we expect Jira to have given the size of your environment. With this info, it might be necessary to also follow Increasing JIRA application memory. Plugin timeouts like these tend to happen because the…

Hi Rick, While the Jira REST API can't directly be used to deactivate users, you could use the embedded Crowd's API built into Jira Server in order to manage user deactivations. Check out the workaround listed in the feature request https://jira.atlassian.com/browse/JRASERVER-37294 From that page: Workaround Use Crowd REST…

Hi Dave, Yes, I would say that having any of these 'com.atlassian.servicedesk' plugins on this table with a 'false' value would keep service desk from being able to start up when jira starts. The SQL can vary slightly depending on what flavor of SQL you are using with Jira (ie Oracle, MS SQL, postgres, mysql for examples…

I tried to recreate this problem in my own Jira 7.12.1 version. However when I click these links (the numbers), I do not get an error. I did some additional research on this I came across this bug: https://jira.atlassian.com/browse/JRASERVER-67891 While it seems to deal with a different but related location, I think it…