I’m trying to find a way to add custom notes and documentation directly to JIRA projects but can’t locate this feature in the default setup. I need something that lets me attach important project information to the main project page.
Basically I want to store project-related details that don’t belong in tickets, code comments, or formal documentation. Things like:
Notes about why certain code structures exist for new team members
Reminders that Developer A modified Component B so upgrades need extra testing
Tracking that Library C is still in beta and needs updating later
I remember FogBugz had a wiki feature for projects. Does JIRA have any addons or plugins that work similarly? I’m open to building something custom if it’s not too complex.
Has anyone solved this problem before? What’s the best approach for managing this type of project metadata in JIRA?
I actually built a simple solution for this using JIRA’s project pages feature combined with shared components. What we did was create a special issue type called “Project Documentation” that stays permanently in our backlog. Each doc issue covers different aspects like architectural decisions, dependency tracking, and team knowledge. The beauty is you can cross-reference these from regular tickets using smart commits and @ mentions. We also leveraged the project sidebar to add quick links to our most important documentation issues. Takes about 30 minutes to set up and doesn’t require any plugins or additional licensing. The search functionality works great too since everything stays within JIRA’s ecosystem. Been using this approach for over a year and it solved exactly what you’re describing without the overhead of maintaining separate tools.
confluence is defo the way to go! super easy to link within jira & keep all ur notes handy. we use it for team stuff & odd code notes too. marketplace has some add-ons, but confluence works best for most teams.
We ran into this exact issue a few months back and ended up using the project description field plus a combination of custom fields at the project level. You can modify the project description to include structured documentation sections, though it requires admin permissions. For more complex documentation needs, I found that creating a dedicated epic or component specifically for project notes works well - you can pin it to your board and use it as a central documentation hub. The Scriptrunner plugin also lets you create custom project pages if you have budget for it. Not as elegant as a built-in wiki but gets the job done without needing Confluence licensing for smaller teams.