About

The problem

Project management tools such as Jira have gotten too feature rich. There are simply too many ways to do the same thing and there is no standard approach across industry.

In Jira you typically track the status of abstract epics, goals and stories. The statuses of tangible outputs, Features and APIs, are lost in the noise.

Requirements, API specs, business logic and designs just get lost in a forgotten pile of completed tickets. Or they get dispersed across a plethora of SaaS applications and markdown files.

How Moon Blocs helps you

Your designs, business logic, API specs and requirements aren't lost. Instead:

• Features are documented using Features.
• APIs are documented using API Documents.
• Written designs are documented using Documents and can be linked to relevant Features and API documents.

You still make tickets using Moon Blocs Tickets. However, they are used to track the granular tasks that are needed to build features and APIs in a Kanban view.

Tracking the statuses of the outputs that matter to decision makers, Features and APIs, is handled automatically with Analytics.

Forget about painstakingly linking tickets across kanban boards. Work collaboratively across teams using Features.

Assign ownership of Features and APIs so you know who to involve when debugging or making changes with Teams.