I’m building a small Forge app called Admin Jump and I’m trying to validate whether the underlying problem is actually painful enough to solve.
The problem I’m targeting is Jira Cloud administration being spread across many different settings screens when an admin simply wants to find a configuration object quickly.
The current beta gives Jira admins one search interface across:
- custom fields
- workflows
- statuses
- issue types
- projects
Search works by name, key, ID, or object type.
I’m deliberately keeping the product small right now because I don’t want to add features before understanding what Jira admins actually need.
I’d really value input from people who administer Jira Cloud:
1. Is finding configuration quickly actually a recurring pain for you?
2. Which Jira configuration objects should a tool like this search that I’m currently missing?
3. What information would need to appear in a result for it to be genuinely useful?
4. Would you keep a lightweight configuration-search app installed, or is Jira’s native admin navigation already enough?
5. What one capability would make something like this worth paying for?
Disclosure: I’m the developer behind the app under Vector Apps.
The beta is already working on Forge. If anyone here is willing to test it on a Jira Cloud site, reply here and I’ll share the private beta install details.
I’m especially interested in critical feedback, if the idea is too small or the problem isn’t painful enough, that’s useful information too.