Should we use the same tool for bugs and feature requests?

One tool: simpler but blurry
Using a single tracker reduces context-switching and keeps all work visible. You only need one login, one search, one set of workflows.
Downside: bug backlogs get cluttered with feature requests. Developers searching for "critical" issues wade through feature ideas. The distinction gets blurry.
Two tools: cleaner separation
Using separate trackers keeps critical bugs isolated from feature discussions. Developers see only bugs. Product managers can evaluate features without distraction.
Downside: someone has to maintain two systems. Duplicate effort. Harder for teams to see the full picture.
The practical middle ground
Use one tool with a clear "Type" field (Bug vs. Feature) and strong filtering. Create views that show only bugs. Developers open the "bugs" view; product managers open the "features" view. Same tool, separate workflows.
What matters most
Pick whichever approach your team will actually use consistently. If developers ignore feature requests in the bug tracker, separation makes sense. If the single-tool view feels cluttered, two tools help.
Recommendation
Start with one tool. Split only if the workflow noticeably breaks down after three months.