You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As a Jira user (non-admin), and an experienced DevOps consultant who has used many tools, how can I tell what options and/or marketplace extensions are currently enabled on my Jira instance?
Why?
Do I need to provide more reasons?
Hello @Nathan Hawk
Welcome to the Atlassian community.
Some apps add something that may make it easy to identify, like a new option on the main menu bar. Others are more subtle, like adding functions to JQL syntax.
Currently the only way for a non-admin to find out what third party apps are installed on an on-premise Jira system they access is to contact the Jira Admins for the system and ask them.
How do I identify/contact a Jira Admin? Let me guess, currently the only way for a non-admin to find out who the Jira Admins are is to contact the Jira Admins for the system and ask them. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately there is not a way in Jira for a non-admin to get a list of Jira Admins.
I would recommend that you talk to the Project Admins for any project you work on. Since only Jira Admins can create projects, the Project Admins may be able to tell you who they contacted to get their projects created.
You could also check with the technical support team for your company. If they don't manage Jira themselves, they may be able to tell you who does.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a common productivity gap I see in tools. System configurations should be accessible by default. This creates unnecessary work and roadblocks. Only secure the parts that should be secured. Don't make everything a mystery to be unraveled.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.