Support for Atlassian Server Products (and apps like BigPicture) is ending in February 2024.

Are you planning a migration to Cloud? Make sure you don't lose your BigPicture data/configurations in the process. Check out this page for information on how to migrate BigPicture's data to Cloud. If you have any questions please email

BigPicture logs - diverting to a separate file

In this article we’ll show you how to set up a separate log file for BigPicture debug data.

If you are getting a sizable amount of BigPicture debug data sent to atlassian-jira.log but would rather divert it to a dedicated log file, you can do it by manually changing the configuration of Jira’s log4j file. 


  1. Add the following snippet to your* file:

    log4j.appender.bigpicture.layout.ConversionPattern=%d %p [%X{jira.mailserver}] %t %X{jira.username} %X{} %X{} %X{jira.request.ipaddr} %X{jira.request.url} %m%n = INFO, console, bigpicture = false AN ADDITIONAL BIG

  2. Restart your Jira instance.

This will create a separate bigpicture.log file for all logs from our app, or from com.softwareplant package specifically).

Where to find the file?

The is located in “WEB-INF/classes/” You can find this path by going to your Jira Administration > System > Logging and profiling, and scrolling down to the “Default Loggers” section.

You can further configure the granularity of the log file by clicking on the “Configure logging level for another file” option, and choosing the desired logging levels.