nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Advice for a solo developer

Eric Pement

What advice, recommendations, or best practices do you have for someone using JIRA as a sole developer? That is, a one-person "team", using JIRA to track features, bugs, and progress in PHP software development?

Accepted answers

Ignacio Pulgar

Have a look at these tips: https://community.atlassian.com/t5/Jira-discussions/What-would-be-your-advice-to-first-time-Jira-Software-admins/m-p/1037390#M6849

All comments

Ignacio Pulgar

Have a look at these tips: https://community.atlassian.com/t5/Jira-discussions/What-would-be-your-advice-to-first-time-Jira-Software-admins/m-p/1037390#M6849

Eric Pement

Hi Ignacio. Thanks for responding, but I was looking for something more specific. I'm less interested in how to be a Jira admin. My question had to do with being the sole person on a development team, in which I assign tasks to myself, track bugs, select features or enhancements to add, and so forth.

If you have further recommendations, I am open.

Ignacio Pulgar

These are my two cents:

Use a scrum board. It counts with more builtin reports than a kanban board, which would let others track your progress.
Describe issues as if a different person were responsible for resolving them.
Use standard naming conventions for versions and sprint names. Sprint names should include the project key, if possible, in single project boards.
Estimate issues. It will help you plan better.