Andy Heinzer Atlassian Team

Hi Thanks for reporting this. Sorry for the inconvenience, there was an incorrect listing within the marketplace page for which version of the UPM was listed as being compatible with Jira 8.1.0 sites. However at this time that has been corrected. So if you visit the UPM in Jira again today, it should be offering you a…

Hi Davide, Sorry to hear you are seeing this problem. I would recommend trying to following steps when you have some time when you can stop Jira. * Stop Jira * Go the $JIRAHOME/plugins/installed-plugins/ directory * Find all plugin in here by the name 'universal plugin manager' and remove these. I suspect you will have at…

Hi Charlie, Sorry to hear that you are seeing this error. However I suspect that this could be cause by using an unsupported platform for Crowd. Could you please let us know: * What version of Crowd this is? * What database type/version you are using with Crowd (mysql, postgres, etc)? * What Java JRE/JDK type/version you…

Hi Jeff, Sorry for the inconvenience, we currently tracking this problem in UPM-5985 So far I believe this is only affecting Jira 8.1.0 installations for this specific plugin. For the time being I would recommend ignoring that update request. I'm honestly not sure what would happen to the UPM to try to downgrade from a 4.x…

Hi Mitch, I don't believe this is a new feature. The sprint report is being generated at the time the sprint is closed. So the expectation with that report is that what you see there is what was in the sprint when it was closed. However when you close a sprint, there is a question of "What happens to issues not completed…

Hi, If I understand correctly here, you are looking to map your LDAP groups within the default group names that grant application access in Jira (such as jira-software-users, jira-servicedesk-users). Jira doesn't have a way to do this exactly in the manner you have presented it (of mapping an LDAP group into an internal…

Hi Karthik, I understand that you're seeing only 401 HTTP error codes return from Jira Cloud REST API. Most of the REST API endpoints require authentication to work properly. In cases where the authentication is inadequate or incorrect, you can see these 401 error codes. In the specific case of Jira Cloud and using the…

Hi Varsha, I did some digging around the Jira database to try to find you a complete answer here. My testing was with Postgresql, the syntax might be different for other database types. I tested this against Jira 8.1.0. For finding which filters are used on Agile/Software boards you can use the following SQL query: select…

Hi Davide, Thanks for reporting this. We are actually tracking a related bug for this over in UPM-5985. I agree that this seems confusing. I would try to avoid updating the UPM until this is resolved. I suspect that the marketplace listing for the UPM might have an error that is causing this update to be prompted to Jira…

Awesome, glad to hear that helped!

@Natasha Denny That is not the correct usage here for searching of such issues with two different linktypes. Instead try using issuelinktype in (blocks, "is blocked by") This will return all issues with either the blocks link type or the reciprocal linktype of 'is blocked by'. You might have another custom linktype called…

@Vik There is a corresponding Jira Cloud ticket for this in JRACLOUD-25640. However I don't know if there is a set timetable on if or when it might be implemented in Jira Cloud. I would watch that issue to see if this is coming to Cloud. If it is, I would expect this to be updated to reflect that.

Hi Mario, I can feel your frustration here in regards to not being able to customize this default issue scheme type. But given that JRASERVER-11222 was closed as obsolete, and from that description, Dave Meyer posted this update: As of JIRA 7 (released on October 6, 2015), new projects are not created using the default…

Hi Ed, Thanks for answering these questions. I'm afraid I don't know what else could cause the behavior you have described here. So I have created a support ticket on your behalf that you can access at https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-471753 Someone from our Cloud support team can take a…

Hi Nenad and Milica, * What version of Jira is this? * Have you tried to delete the existing mail handler yet, and then try to create a new one with the new desired settings? * Are you using any automation style plugins with Jira, such as Automation for Jira, Scriptunner, Power scripts, JSU, etc that might be…

Hi Tobias, It is possible that this import caused an upgrade to happen, and in turn if that upgrade task failed in one or more ways, it could have caused this behavior. * What version of Jira was the backup taken from? * What version of Jira was the backup restored to? Depending on the answer to those questions, it might…

Hi Dmytro, In the current versions of Jira Cloud, it is not possible to customize these right click menus on a board and create your own links. However there is an example feature request for this over in JSWCLOUD-8784 In the meantime, have you tried using the keyboard shortcuts? In a Jira Cloud Software board, you can…

Hi Matt, If I understand your situation here, you have deleted the request type that is causing this warning to appear. However I am curious to see if you can click that link in the first screenshot to the 'fields' page. My thought here is that perhaps you have another request type in question that might have the approvers…

Hi Andy, I see you had a related post over in https://community.atlassian.com/t5/Confluence-questions/email-change/qaq-p/1069101 that appears to be resolved. However I wanted to check with you to make sure that you can still login to your Jira Cloud site and the https://id.atlassian.com site successfully. If you cannot,…

Hi Ed, I too am scratching my head at this one. At first I thought this might be a difference between either a next gen project and a Classic project in Jira Cloud, but I don't see any difference in the way attachments are presented in these two. It could be different in a Jira Service Desk project, but only in regards to…

Hi Suresh, Atlassian's Jira Cloud has deprecated the use of plaintext passwords for basic auth type REST API requests. More details are in https://developer.atlassian.com/cloud/jira/platform/deprecation-notice-basic-auth-and-cookie-based-auth/ In place of using a clear text password, you can still use basic auth, but you…

Hi Rob, Sorry to hear you're having this XML backup problem. What version of Jira is this? The behavior you describe is strange. I would not expect Jira to give you this kind of response to a backup request. Is this by chance a large or Enterprise scale Jira site? You can compare your site statistics against our guide in…

Hi Arjen, Yes, Service Desk can help here. However it might depend on the version of Service Desk you have, and the settings of that project. For the sake of my testing, I know this works in the latest 4.1.0 version of Service Desk, if you don't see these same settings in your version, please let me know what version you…

Hi Lee, There are different levels of users for starter licenses among different products. For example, Jira Core and Jira Software have starter licenses of 10 users each. However in this case, you're using Jira Service Desk, which has a starter license user limit of 3 Agents. You can see this list among products in…

Hi Saurabh, When you integrate Jira with an SSO like Crowd, Jira no longer handles the authentication of users. Instead Crowd handles that. You can also find note of this in the guide: Retrieving the JIRA Administrator Using Single Sign-On (SSO): * If JIRA is configured for SSO through Crowd or another third-party service,…

Hi, Are these issues being set with a resolution value when closed? Most workflows will set this when issue reaches this status, but if your workflow was customized and changed or removed this post function it might account for this. Also when you look at these issues in the last column of the board, are the issue key…

Technically, no it is not mandatory. You can still use MySQL 5.6.x with Jira 8.1.x per our supported platforms page. However we know the character limitation in that version of MySQL has been a thorn in the sides of Jira administrators for a long time a la JRASERVER-36135. So I would still recommend going to a 5.7 version…

@Luke Gavel It depends on the version of MySQL you're using on the backend. If you're using a MySQL 5.7.x with a Jira 8.x.x version, then our own documentation (Connecting Jira 8 applications to MySQL 5.7) recommends to use the utf8mb4 character set and collation because we know it will help you avoid the problem of…

Hi Matt, I don't recall seeing this kind of error in a Service Desk project. Could you please let me know: * What version of Service Desk is this? * What this misconfiguration warning looks like? (a screenshot would be awesome) * Does this warning give you any specific details about the field name/type in question? I would…

Hi Rinaldo, I'm not sure yet how to best explain these connections yet, but I have a hunch. With Jira and Jira Service Desk there are two different types of connections that would have the Jira application establishing Mail connections: Incoming mail and outgoing mail. The incoming mail to Jira are message end users send…