We have one Jira project that the app "PagerDuty Incident". The app displays on every Jira issue ticket, which creates a lot of noise and distraction. I want it to be removed for teams that do not use it.
Can some apps be removed for specific Jira projects? Or enabled for select teams only?
Jira does not have a framework for "apps by project" - apps are installed at a system level and become globally available. That is just the Jira framework though.
There are a lot of apps that provide per-project configuration, some even need to be actively enabled by an admin in each project, although most make themselves available and then do nothing if there's no config for them in a project.
Only a handful of apps work on "enable by group", most go on the principle that people collaborating on a project should probably see and use the same things.
So, TLDR: only if the PagerDuty Incident app supports by-project settings.
If I recall correctly, PagerDuty doesn't allow that. We had it enabled last year before we switched to OpsGenie, and I think their support people told us it wasn't configurable on a project basis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm finding that most apps don't embrace this. Is there a feature request out there to allow at least controlling the visibility of apps on each issue. It's pretty annoying to see apps specific to our Dev team's project show up on my service desk.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mack Baczynski I don't think this is a Jira limitation; it's on the various app developers to code to those specifications. For example, the X-Ray testing suite is installed at the system level, and there's an entry for project-level config in the settings of each project. I can't hide the config in the project settings, but I can use the project-level config to make sure that X-Ray functionality doesn't show up on tickets in projects that are not using it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then Atlassian should not accept apps in the Atlassian Store unless they are coded to spec!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They can't check every detail on every app, but they do do some checks. In this case though, it's irrelevant. The spec for an app doesn't have to (and in some cases, simply can't) include "be able to be set on a project by project basis". That's not up to Atlassian to decide, it's up to the vendor.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.