Requirements traceability in Jira — is setup the real problem?

Marketplace General Discussion
,
1

I’m considering building a very small requirements traceability app for Jira, and I’d
like a sanity check before writing any code.

Reading reviews of existing tools, the complaint I see most often isn’t about missing
features — it’s about setup. One review of a major tool says the reviewer gave up
configuring it and moved to another product. Others mention new issue types filling up
the backlog.

So the idea is deliberately small:

  • Shows requirement → issue → test as one tree, using the issue links you already have
  • No custom issue types, no project configuration, no admin setup
  • No baselines, no regulatory templates (if you need those, the existing tools are better)

Two questions:

  1. If you’ve used a requirements tool in Jira, was setup actually a problem for you, or
    am I over-weighting a few reviews?
  2. Would “no setup, fewer features” be a reason to switch, or does switching cost more
    than the setup pain it saves?

I’d rather find out that this isn’t worth building before I build it.

2

Hi @ogosso.bubble,

No view on the switching half, I’ve never run one of these in anger. But on setup, the reviews look right about where it hurts: the issue types, not the links. Xray auto-creates its “Tests” link type at install, so that layer is already free. What’s left to configure is the types themselves, coverable-item mapping and a coverage hierarchy, and its own quick-setup page tells you to ask a Jira admin if you don’t have the permission.

So “no new issue types” may be the sharper pitch than “no setup”. Which tool were those reviews about?

3

Hi @ogosso.bubble,

I agree with you that it’s smart to do this sort of research before building your app. My advice is to ask this question over in the Jira Cloud Admins community. I think you’ll reach a lot more of your target market over there.

https://community.atlassian.com/forums/Jira-Cloud-Admins/gh-p/JiraAdmins

Just be careful how you ask your question so as not to violate any of their community rules. I see people routinely conducting research by framing questions on potential pain points in Jira rather than framing questions as ‘should I build an app for this’.