I’m new to a startup that uses JIRA for project management. It’s been a while since I’ve used this tool and I’m struggling with how to handle big-picture planning.
In my last job, we used Azure DevOps. There, I focused on Features for most of my work. Epics were just for very high-level stuff. I’d do all my research and planning at the Feature level, then break those down into user stories for the team.
Now I’m confused about how to manage and prioritize large projects in JIRA. I can’t find an Epic backlog, and I’m not sure how to compare and rank big projects against each other.
Am I missing something about how JIRA works? Or do I need to rethink how I approach project planning?
I’ve heard some people use other tools like Product Board alongside JIRA. My new team is actually using a spreadsheet for what I’d call Epic management, which seems odd to me.
Any advice on how to handle this in JIRA would be really helpful. Thanks!
hey there, i had similar probs. jira can be weak for big picture planning. we use jira with productboard to handle epic/feature stuff and then connect to jira for everyday tasks. spreadsheets may work if budget is tight.
JIRA can be tricky for high-level planning, especially if you’re used to other tools. In my experience, setting up a custom board or filter for Epics can serve as a pseudo-Epic backlog, and utilizing custom fields or labels helps with prioritization. For Features, since there’s no native support in JIRA, many adopt alternatives like custom issue types or external tools such as Product Board and spreadsheets to maintain oversight. This approach might initially seem clunky, but with the right tailoring to your team’s workflow, it can effectively bridge the gap between strategy and execution.
As someone who’s been in your shoes, I can totally relate to the struggle of adapting to JIRA for big-picture planning. In my experience, JIRA’s strength lies more in task management than high-level strategizing. That said, there are ways to make it work for larger projects.
For Epic management, I’ve found success in creating a custom board specifically for Epics. It’s not a perfect solution, but it gives you a bird’s-eye view of your major initiatives. To prioritize, we use a combination of custom fields and labels. It takes some setup, but once it’s running, it’s pretty smooth.
As for Features, you’re right that JIRA doesn’t handle these natively. We actually faced the same dilemma and ended up using a hybrid approach. We create Features as a custom issue type in JIRA, linking them to their parent Epics. For the actual prioritization and roadmapping, we use an external tool (in our case, Aha!) and then sync the key info back to JIRA.
The spreadsheet approach your team is using isn’t uncommon. It’s a quick fix, but in my experience, it becomes unwieldy as projects grow. If budget allows, I’d recommend looking into a dedicated product management tool to complement JIRA. It’ll save you headaches down the line.
Remember, every team’s workflow is unique. Don’t be afraid to experiment until you find what works best for your startup. Good luck!