Set up Backlog with Git, Slack, and Jira: A quick-start guide

Whether you’re migrating from Jira, managing code with Git, or streamlining collaboration in Slack, Backlog makes it easy to connect your tools and keep your team working as one.

With just a few simple steps, you can cut setup friction and build a workflow that fits right into how you already work.

In this guide, we’ll walk you through how to:

• Import Jira projects into Backlog
• Connect Git repositories and manage size limits
• Integrate Backlog with Slack to create issues and receive updates.

Let’s get started!

Migrating from Jira to Backlog

Switching from Jira? Backlog’s Jira Importer helps you bring your project data into Backlog with minimal hassle.

Before you begin

To avoid migration errors, we recommend creating a new project in Backlog before importing your Jira data. This ensures a cleaner transition and stops any data conflicts in existing projects.

Here’s what you’ll need:

• Java 8 installed
• Admin access to your Backlog Space
• The .jar file for the Jira Importer (available on the support page).

Note: The Jira Importer is currently in beta. Migration is only supported on Jira Cloud and specific server versions (e.g., 6.3.4). Keep in mind that change logs and some status settings may not migrate fully.

Key limitations

Some limitations apply to the migration process, so keep these in mind:

• Status migration: All issues are imported with the status set to “Open.”
• Change logs: These are not currently supported.
• User conversion: Users are not automatically converted. Instead, they’re registered as fixed values in lists.
• Field behavior:
  • Boolean fields become radio buttons (Yes/No).
  • Date/time fields are converted to plain dates.
  • Project keys are reformatted to meet Backlog requirements (hyphens → underscores, lowercase → uppercase).
    
• Custom fields: Only supported on Max or Platinum plans (Japan plan types).
• Free plans: Migration is not possible due to API rate limits.
• No parallel usage: Running the importer in parallel may exceed API limits.
  

How to migrate your Jira project

1. Download the .jar file and open your terminal.
2. Run the importer using the required command structure (see support page).
3. Select the Jira project you want to import.
4. Choose the new Backlog project as your destination.
5. Review the mapping and confirm the migration.
6. Once complete, check the imported issues in Backlog to verify accuracy.
   

Pro tip: Use this time to clean up old or redundant issues before importing — your new project will be easier to manage from day one.

Setting up Git in Backlog

Git is a powerful version control tool for tracking code changes and collaborating across teams. In Backlog, Git integration is built-in, making it easy to work on code directly within your project space.

Enabling Git

To enable Git for your project:

1. Open your Backlog project.
2. Click “Git” in the left-hand menu.
3. Select “Enable Git”.

Once you’ve enabled Git, you can create multiple repositories per project. This is particularly helpful if you’re working on separate components or services.

Note: Only project administrators can enable Git.

Accessing Git

After enabling Git, project members who don’t have restrictions on their account can view all available repositories on the “Git” project page.

To access a repo via HTTPS:

• Use https://[Space ID].backlog.com/git/[Project key]/[Repository name].git
  • E.g., https://demo.backlog.com/git/BLGDSGN/cat-robot.git
  • Can’t be accessed via a browser
• Enter your Backlog login info. If you’re using two-factor authentication, enter the special password generated in your Backlog personal settings.

To access via SSH:

• Generate a SSH public key.
• Register the key in your Backlog personal settings.
• Use [Space ID]@[Space ID].git.backlog.com:/[Project key]/[Repository name].git
  • E.g., demo@demo.git.backlog.com:/BLDGSGN/cat-robot.git

Checking repository size

To monitor your Git repository size:

• Go to your profile icon → Space settings → Disk usage to view total usage.

Or, to check a specific repo size, use the following commands:

Clone your repository
git clone [https url of your repository]

Change your current working directory to the repository
cd [directory of your repository]

Pull all remote branches to your local repository
git pull

Check the size of the .git directory
du -sh .git

Managing size limits

Working with large files or oversized repositories can lead to problems when pushing, cloning, or performing other Git operations. Backlog applies specific limits on file and repository sizes to help you avoid these issues.

• The maximum file size for Git pushes is 100MB. 

If you try to push a file that is over this limit, you’ll encounter an error. To fix this, either remove the large file from your commit, or use a tool like Git LFS to manage large assets. Keep in mind that even deleted files remain in the commit history — so removing them from your local repo won’t reduce overall size unless the history is rewritten.

• The total repository size limit is 10GB.
• System warnings will appear as your repo grows — specifically at 1GB, 5GB, and again at 10GB. 

Once you have reached your 10GB limit, the repository becomes read-only, and blocks further push attempts.

To fix this, you’ll need to create a new, smaller repository using the latest commit from the original repo. 

This involves a few terminal commands to clone the latest state and reset your Git history. (We’ve outlined those below.)

To reduce size:

Set the URL of the current repository
src_repo=${[ the URL of current repository ]}

Clone with –depth 1 option
git clone –depth 1 ${src_repo}

Change your working directory to the repository
cd <the directory of the repository>

Set the latest commit message
from_commit=$(git log -1 –pretty=%H)

Delete .git directory
rm -rf .git

Initialize your repository
git init

Add all files to Git
git add .

Commit with the comment of the latest commit message
git commit -m “from ${src_repo} ${from_commit}”

Set the URL for the new repository
git remote add origin <new url of repository>

Push to the new repository
git push origin main

Pro tip: Regularly review large files and remove unused assets. For ongoing needs, use Git LFS for large file support.

Integrating Backlog with Slack

Backlog’s Slack integration helps your team stay in sync without switching between apps. You can create issues, get project updates, and receive personal notifications — all from inside the Slack app. 

Adding the Backlog app

To get started, add the Backlog app to your desired Slack channel or direct message thread.

Once added, you can use commands like:

Command	Action
/backlog add	Add a new issue
/backlog link	Link/unlink a project
/backlog logout	Log out from Backlog
/backlog help	See available commands
/backlog settings	Set personal notifications

Adding issues from Slack

You can add issues to Backlog in three ways:

1. Using /backlog add
2. Via the global shortcut (Slack lightning icon)
3. Via the message shortcut (hover over a message → More actions)

When triggered, a dialog box will pop up:
Select your project from the dropdown. Them, add the issues details (title, description, etc.) to the relevant fields.

And finally, click “Add Issue”. 

Note: It’s not possible to add issues to a project via Slack if your project needs custom fields. 

The Backlog app will send you a message, so long as there are no issues with your request. To edit the issue after this point, click “View issue” in Backlog and the issue will be opened.

Getting notifications from Backlog 

To link a Backlog project and start receiving notifications:

1. Use /backlog link.
2. Select the desired project from the dropdown.
3. The project will now appear in your linked list.

To unlink a project, click Unlink next to its name.

Receiving personal notifications

To get direct messages in Slack when you’re mentioned or assigned in Backlog:

1. Enter /backlog settings in the Slack message input field and hit “send”
2. Click “Enable” to start receiving notifications.
3. To stop, use the same command and click “Disable”.  (This option will appear if notifications are currently enabled.)

Note: You can only link projects where you’re an admin.

Logging in and authentication

When you perform an action for the first time, the Backlog app will prompt you to log in.

Click Login in the Slack message, then click “Allow”. 

Review and allow Slack workspace permissions. Then select your Backlog space and enter your credentials.

Allow final permissions to complete the connection. Once done, you’ll see a success message. You’re all done, and you can close the screen. 

After closing and returning to Slack, you’ll get a private message from the Backlog app telling you that the login was successful. 

Help and shortcuts

To see available commands and access quick actions:

• Enter /backlog help
• You’ll get a response with:
  • All command explanations
  • Buttons for Add Issue and Manage linked projects
  • A link to the Help Center.

Pro tip: Save time by bookmarking the /backlog help output for fast access to all features! 

Final tips for a smoother setup

Here are some quick ways to boost your productivity as you connect your tools:

1. Test integrations on a staging project
   Before rolling out across your entire team, test your Jira import or Git access in a sample project.
   
2. Use naming conventions
   For Git repos and Jira-imported projects, consistent naming helps with searchability and organization. E.g., Client_Project_2025Q1.
   
3. Communicate changes
   If you’re linking Slack or enabling Git, inform your team so everyone is on the same page — and ready to collaborate.
   
4. Monitor storage early
   Git repo sizes can creep up quickly. Keep an eye on warnings and optimize regularly.
   
5. Bookmark the Help Center
   Nulab’s support pages offer walkthroughs, visuals, and troubleshooting tips to support you every step of the way.

You’re ready to go

By setting up Git, Slack, and Jira integrations in Backlog, you’re laying the foundation for a connected, collaborative workflow.

You can:

• Migrate from Jira without losing momentum
• Work on code with built-in Git support
• Stay updated in Slack without leaving your conversation.

Now it’s your turn — log into Backlog and start building a workflow that works for your team!