An image of Unito's flow list with the Notion logo and smiling faces.
How To Report on Development Work With Notion and Jira
An image of Unito's flow list with the Notion logo and smiling faces.

How To Report on Development Work With Notion and Jira

Do you know what your developers are up to? Whether you’re working in a tech company or an organization with a software development arm, you’ll need to collaborate with developers. These collaborators are some of the most specialized, hard-working people you can find, but their work is often the most siloed. But because their work is so essential, people throughout the command chain need updates on development work. 

Here’s how you can provide save yourself that work by combining a flexible tool like Notion with Unito’s deep integrations.

Why report on development work?

Developers are incredibly siloed. Their tools are intensely specialized, and they’re not usually a good fit for other teams. That means developers usually have their own tool stack, while the rest of the organization uses a separate work hub.

Without the right integration, working with developers can be tough. You need to use emails, meetings, or chat messages just to get in touch with them. If you’re an individual collaborator who needs updates on a specific task, you can probably get by. If you’re a stakeholder with dozens of things to take care of, you don’t have time to crawl through emails for the right update. 

In Unito’s Report on Reporting, 82% of people surveyed said their reports led to actionable insights at least most of the time. With the right report, a development team can easily communicate updates, workload, and find the weaknesses in their workflows. But reporting involves a ton of manual work, it means consolidating data from multiple sources, and it’s a huge time-sink.

Why use Unito and Notion?

Mainly because this combo means you don’t have to build manual reports.

Notion might just be one of the most flexible work management tools out there. Users can build wikis, databases, spreadsheets, project management platforms, and more. With its simple interface, you don’t have to be a technical user to get the most out of this platform. For this use case, a Notion database is a simple way to collect information from Jira and turn it into a quickly digestible overview.

Unito is a no-code tool with the deepest two-way integrations on the market. Build flows between tools and you can sync crucial data back and forth between them. No more copy-pasting and no more status meetings. Combine Unito with Notion, and you can build powerful reports that are automatically updated with information from your work tools.

Here’s how it’s done.

Building a development report in Notion

Because Notion is so flexible, you can build your report any way you want. Or you can use the template we’ve already created specifically for this use case. The columns in this template replicate the most valuable Jira fields to give you a better idea of what’s going on. Let’s go over them.

  • Issue summary: A title field in Notion that will pick up the name of a specific Jira issue.
  • Issue number: Issue numbers are used as shorthand in Jira for quick reference. In Notion, this is a number field.
  • Issue type: There are four main types of issues in Jira. Tasks represent pieces of work that need doing, while bugs are for tenacious software problems. Epics and stories are used to direct software work. This is a select field in Notion.
  • Priority: How important is this issue? Another select field, here.
  • Status: How’s progress on the issue? This select field in Notion can also be used to create columns for a Kanban board.
  • Due date: When’s it due? A date field.
  • Assignee: See who’s responsible for a specific issue using a person field.
  • Labels: A multi-select field that can be used in a myriad of ways, like determining which part of a software project is touched by an issue.
  • Estimated and time spent: Two number fields used to see how much work is going into specific issues.
  • Link to project: This URL field will let you go to an issue’s Jira project in a single click.

Once you’ve found your way around this database, you can also create alternate views for your use case. You can filter by specific fields, sort issues how you like, and more. We’ve created a few alternate views for demonstration purposes, like the Overdue Bugs view, which automatically filters Notion rows that have due dates earlier than the current date.

Now that you have your Notion report built, it’s time to fill it up.

Populating your report with Unito

To get data from Jira into Notion, you need to build a Unito flow. Don’t worry! It can be done in just a few clicks.

The first step to building your flow is connecting Notion to Unito.

Note: Because Notion’s integration is in beta, there are specific installation instructions to keep in mind. Consult our Help Center to learn more.

Next, pick the projects you want to connect. You’ll want to choose the Notion report on one side and the Jira project you want to report on for the other.

Now it’s time to set up flow direction. For most use cases, a two-way flow is essential for keeping both projects updated in real-time by creating new work items in one tool whenever you do that in the other. In a reporting situation, you don’t want new Notion rows to be replicated in Jira, so make this a one-way flow.

After choosing flow direction, you can set up rules to filter out Jira issues you don’t want in your report. You could filter out issues with specific assignees or labels, for instance. This part is entirely up to you. You can see how it’s done at our Help Center.

After the rules screen, it’s time to customize your field mappings. For many integrations, Unito can automatically map similar fields. To make Unito work with this use case, you’ll need to add each field mappings. It’s dead simple, though! Just click on + Add mapping

Then click on each dropdown to match the fields on the Notion side with the appropriate Jira field.

Exact mappings might vary for your use case, but this is generally what you want.

Your fields should be mapped for two-way updates. Even if you don’t want new Jira issues to be created when you create new rows in Notion, you still want everything kept updated in both directions. This allows stakeholders to change labels, add comments, and more in Notion, knowing everything will be synced over to Jira.

Once all your fields are mapped, you’re done! You can launch your flow and watch as Jira issues get synced over to Notion. Build flows for other Jira projects, and you could have a single Notion database become a report for everything your development team is doing.

Essential Unito features for this use case

One-way create, two-way update

That’s the term we use to define the flow we just set up in the previous steps. By customizing your flow with this feature, you make sure all information is kept updated across both tools without the creation of new work items. This is especially important if you sync multiple Jira projects to a single Notion database — otherwise you’ll get Jira issues traveling from project to project.

Custom fields

Jira uses custom fields to give users more control over their projects. With Unito, you can sync these fields from Jira to other tools — and back — so that you don’t lose the customizability of your tools. You can sync up to one custom field with a Team plan, and unlimited custom fields with the Company and Enterprise plans.

Advanced mappings

For many integration solutions, you’re a bit stuck with what the tools give you. That makes it tough to truly recreate the environment from one tool in the other. Unito lets you customize your field mappings so that isn’t the case. When you’re using a flexible tool like Notion, that’s essential.

Ready to automate your reports?

Try Unito for 14 days, absolutely free.

Try it free