Andy Heinzer Atlassian Team

Hi Mik, Not all packages in Jira have logging that you can configuring with in the application natively. However what you can do is try to see if you can set the specific logging level for that package to see if this works. To do this, you would need to first navigate to the Logging and Profiling page in the System menu.…

That sounds strange. My concern would be to understand if maybe this isn't a project permission problem, but an application access problem. With JIra 7, there is a different way of managing which users have access to applications like Jira Software and/or Jira Service Desk. Since Sprints and backlog view are specifically…

Hi Terri, There are a couple of different ways to do upgrades when it comes to Jira, these are explained in Upgrading Jira Applciations. Personally I am a fan of the Fallback method. Mostly because it provides the clearest way to revert should the upgrade not work as expected. In regards to your specific situation: I would…

Hi Kamil, Thanks for this additional information. In order to help us troubleshoot this issue, I would like to see if we can gather logs from your system. In order to do that, I created a support request on your behalf. Please upload the logs to that link. Regards, Andy

Thanks for this info Maurice. I am interested to see if perhaps the "Generic Event" is causing you to still get notifications of this kind of change because you are the reporter. Could you try to adjust that notification scheme to remove the generic event notifications for reporter and then see if this same kind of change…

Hi Robert, There is an open feature request to allow this to be hidden completely from users in https://jira.atlassian.com/browse/JRASERVER-62709 And while users can click that button I highlighted in red in order to collapse that pane, Jira users that can login to this page are expected to be able to see this project…

Hi Chrys, There are a couple of different solutions. You could completely remove the 8080 connector from the server.xml at which point no one could connect there, or you could make sure that this 8080 connector has a redirect parameter in it such as <Connector acceptCount="100" bindOnInit="false" connectionTimeout="20000"…

Thanks for letting us know the solution here, Doods!

That file exists in the $JIRAINSTALL/conf/ directory. As for guides on how to configure this, since you mentioned using Apache to handle SSL, I would recommend this guide: Integrating JIRA with Apache using SSL. This guide provides some sample configurations that should be setup for that kind of configuration.

Hi Jonathan, That specific page is how you can turn off this popup view for Core Boards. The page in your screenshot is from /secure/admin/AdminLabs.jspa However, that only effects Jira Core Boards, not the Software boards like kanban and scrum. In order to turn this popup issue detail view feature off for Jira Software…

Issue Updated actually encompasses lots of other events, such as Assignee Changed, Issue Created, Comment Added, etc. (by that I mean if you change the assignee of an issue in Jira, you can only do that by updating the issue.) The issue updated is probably the most generic event notifications can be sent on in Jira. But…

Oh sorry. I've added the tags for that plugin and the marketplace tag to this post.

Hi Hari, I am not certain of the exact cause here yet. But I found a previous created Cloud bug ticket in https://jira.atlassian.com/browse/JSWSERVER-13517 This case had the same error generated as yours. However ultimately this was closed as not a bug. In that case it was because the API call was trying to set an epic…

Personally I would recommend using the format of day-MonthName-year, in the format of d/MMM/yyyy or 10/Oct/2017. I find this kind of format tends to be much more clear for users for both formats. This way there is no ambiguity as to which field is day and which is month. Jira will let you customize the dates to all appear…

Hi @Egor Voynov Just curious if you were able to disable this Jira Labs feature that shows the issue detail view as a popup. You can go to your Avatar in the top right of the page and click the Profile link. On your profile you can disable this Issue Details View labs feature. When this is disabled, you will then see the…

Hi @Jarrad Powell Just curious if you were able to disable this Jira Labs feature that shows the issue detail view as a popup. You can go to your Avatar in the top right of the page and click the Profile link. On your profile you can disable this Issue Details View labs feature. When this is disabled, you will then see the…

Hi Jonathan, I am afraid that this new popup window for the issue detail view does not currently honor the fields set to display there in the board. There is an existing bug for this in https://jira.atlassian.com/browse/JSWCLOUD-16401 In the meantime, you should be able to disable the feature that causes this issue detail…

I am not sure I understand what you are seeing here. When looking at the issue details page, by clicking the More menu, you typically should only have options like so: But it sounds like you might have different options here. If so, I am not sure I understand exactly how that customization might have been accomplished for…

Hi Hugo, Thanks for letting us know your solution here and how you found it.

Hi Ryan, If you're using the Automation feature that is included in Jira Service Desk, that option to send email won't actually allow you to enter an explicit email address there (like user@example.com). Instead this automation rule is only able to send emails to the reporter of the issue and/or requested participants on…

The screenshot you posted is of the Jira Core notification scheme. Service Desk customers have never been notified via those settings. Those specific setting are only for sending notifications to Agents or other Jira Core/Jira Software users that might be involved in that issue. This distinction is also explained in JIRA…

Sorry, which sidebar are you referring to? If this is the left side project navigation bar, then you can collapse this by clicking the box at the bottom of the screen: If this isn't the sidebar you are referring to perhaps you can grab a screenshot to let us know which specific page/area you are asking about.

Hi Pantelis, Sorry to hear about this problem. I have created a new bug for this problem in https://jira.atlassian.com/browse/JSWSERVER-16243 I would recommend watching this issue for updates. As for possible work-arounds until this issue is resolved: * It might be possible to avoid this problem by migrating the Jira…

If you're Jira instance is running 7.4 or higher, then your Jira System Admin could grant you project level admin access. This would allow you to make changes to the workflow of this specific project, but not other projects or system wide settings. This feature is mentioned in the 7.4 release notes. In order for this to be…

Hi Chrysovalantis, I understand that you are trying to configure SSL for Jira, but after doing so Jira can't be started. If this is Jira 7.3.x or higher, then I believe I know the problem here. There is an existing bug in the Jira Configuration Tool that sets the incorrect protocol for the $JIRAINSTALL/conf/server.xml…

You are not mistaken, Jira has never been officially supported on MAC. The supported platforms documentation do not list that OS. That said, it can run.

Alexey is talking about Workflow properties if that wasn't clear from his response. You could use a property such as than on the Closed step of the workflow to prevent users from changing closed issues. You could also add a properly such as: jira.permission.attach.group = Group-name You could use that property on a closed…

Hi Roger, Sorry that this specific Labs feature was not disabling as expected. I was able to reach out to our Cloud support team to help with excluding your Jira Cloud instance from the specific program that enabled this popup window for the issue detail view on the boards. At this point, your Cloud instance should now be…

Adam, That's right, in 7.4 the JTDS driver is already included with Jira. With 7.4 you will want the dbconfig.xml file to have these kind of example entries: <url>jdbc:jtds:sqlserver://andysqlserver123:1433/jiradb;instance=MSSQLSERVER;autoCommit=false;integratedsecurity=true;domain=example.com</url>…

Hi Chris, I can call that REST API endpoint successfully when using the full URL inside double quotes. So it is not clear to me why your instance would generate a 400 bad request error here still. I was able to do this repeatedly with my Jira Cloud test instances using the steps I posted above. I went back the developer…