Do Not Create Jira Graveyards in Confluence

If you are responsible for project management, please read this post carefully. This content is prepared for you.

When a product team, developers, or leaders create a copy of Jira in Confluence, I feel disgusted.

Why does this happen?

Commenting and discussing a specific functionality should be placed directly in the specific task in Jira. Everything related to the conversation about the scope of a given functionality should be in one place.

Confluence is not meant for creating tables that summarize progress on functionality. This is asking for trouble and duplicating work. It only gives the illusion of seeing "where the project is." What's the point of creating a beautiful table with listed and nicely commented links to tasks if someone simply adds a new task related to these ones in Jira the next day? Seriously, are you going to review Jira again looking for that new task to update your summary?

I don't understand. Really.

I've had the opportunity to see even task STATUSES (!?!) presented in Confluence (written manually as one of the columns in the table). I seriously don't know what problem this is supposed to solve. Project management tools exist so that tracking work progress happens there.

Want to prepare a work summary? Use reports and you'll get what you expect.

Sooner or later, there will come a point where what is manually added as task status tracking in Confluence will diverge from the actual progress.

There is no other possibility. I don't believe there is.

This is a waste of time and a complete confusion of tools. Jira should serve as the center of information about project status and dependencies.

Have you ever seen anything like that with your own eyes?

~KB