Top 6 alternatives to Jira’s most-voted feature requests

Learn how Coda can deliver the data your team’s been waiting for.

Project management software is an essential tool for managing and executing projects. Having the right software is crucial for running and planning projects so that all kinds of bottlenecks can be prevented before they lead to a disaster. In some cases, you might be using project management software that mostly fits your needs, although it might have issues that leave your team stuck on occasion. Jira initially launched as an issue-tracking system, and it eventually expanded to planning and tracking projects. While Jira has grown into a project management tool, we’ve heard from teams that the tool has lingering issues—some of which have been around for over ten years. Because Coda optimizes for customized solutions for teams and projects of all shapes and sizes, we decided to address the top-voted suggestions in Atlassian’s public issue tracker for Jira Cloud and Jira Data Center. Here are six things you can do in Coda instead of waiting around for a Jira fix that may not come.

1. See issues from other projects in a single team-managed Jira board or view.

In Jira, you can’t view issues across different projects on one board. You can only view issues for that specific project. This means extra clicks and more balls in the air that need to be tracked when managing multiple projects.

Every Jira issue from every project synced to one view in Coda.

Coda fixes that by syncing all issues for all Jira projects into a single sync table, making it easy to sort, filter, and visualize the issues in one place, like a table, kanban board, and more. You can do this by opening the options of a sync table and adding each project that you want to aggregate. Save yourself some steps by using this template.

2. Customize fields on cards in the Jira backlog and board.

In Jira, you can customize the view in the issues panel. However, when using the backlog and scrum board, you only see the following: the due date, the priority field, and the estimation field. You’re stuck with the default view.

Coda’s kanban board of Jira issues with customized fields.

In Coda, you can customize the table and view any field or property from your Jira issues on a card. After you sync in the Jira issues, you can configure each view by clicking the columns prompt and then selecting any arrangement. This can be done with the backlog and board tables, as well as the issues table. Each project has its own set of challenges, and flexibility is needed to tailor that unique information. Use our free template so that you can create any view in the backlog and board that your projects need.

3. Allow multiple Jira boards in team-managed projects.

In team-managed projects, Jira lets you create one board per project. Multiple boards only exist in company-managed projects. There are workarounds, such as creating sprint “containers” or creating multiple team-managed projects––but these are additional, unnecessary steps. In Coda, you can create multiple boards for a team-managed project, with each board filtered and customized to a specific team, product area, or sprint. You can do this by syncing in the Jira issues and then filtering the main issues table into views for each team. Get started with creating multiple boards in Coda with our free template.

4. See subtasks in the Jira timeline.

In Jira, if you’re on a team-managed project and you drill into the subtasks for a parent task, you won’t be able to view them on a timeline.

Subtasks timeline for Jira issues viewed in Coda.

Using our template in Coda, you can sync in your Jira issues and then view the subtask timeline. All the subtasks are grouped into each issue, so you’re easily able to see the subtasks associated with that issue. If you hover over each subtask, you’ll be able to expand into all of its details. Gain more visibility into all of your subtasks with our free template.

5. Easily view epics from other Jira projects.

In company-managed projects in Jira, you can’t view epics from other projects. This means you can’t see dependencies and deadlines between projects. In Coda, you can view your Jira epics and issues across all projects in one place. After you sync in Jira data, you can use our template to create a timeline view. On the timeline, you can expand and collapse projects so that you can quickly view the associated tasks and epics. Below the timeline in our free template, you’ll find a table view of the same data where epics are grouped. Here’s our free template that lets you tweak the tasks and epics to manage projects the way that works best for you.

6. Automatically sum estimates from Jira subtasks.

When you add original time estimates to subtasks in Jira, the parent issue doesn’t properly show the sum of those original time estimates. The time estimate is properly summed when viewing the parent issue or story on the backlog, but the issue detail view doesn’t show the sum. Furthermore, these time estimates don’t carry over when exporting data.

Using Coda to sum estimates of Jira subtasks.

In Coda, you can automatically sum the original time estimates from subtasks. After you sync in the Jira data, you can view a table of all the subtasks along with the original time estimates. If there are multiple projects synced, you’re able to quickly toggle which projects you want to see the sum calculations for. This table view also includes a separate section for each issue type, so that you can view by stories. An aggregate sum formula is programmed into this template so that you can also see the sum of each story’s subtasks. A visualization of all of this data can be accessed in this free template.

Unblock your team with Coda + Jira.

These six alternative solutions to Jira’s most-voted feature requests can be done quickly (and for free) in Coda. To get started, click the button below, which leads to a compilation of these solutions. Click on a solution, then click on “Copy doc” at the top right of your screen.

Related posts

Explore more stories about the tools you use.
3 reasons to move from Confluence to Coda

Your team deserves more than a wiki.

How to integrate OKRs with agile epics

Integrate your objectives and key results (OKRs) with your epics (agile).

3 reasons why Google Docs is the wrong tool for PMs

Managing my PM work with Google Docs was a huge mistake.