How do I disable/enable the plugin for specific projects?

[Tom Nugter]

It would be great if there would be a way to disable or enable this plugin for only specific projects in our JIRA. Would this be possible? At the moment it seems that you can only enable or disable the plugin for all projects.

[Anthony De Moss · Accepted solution]

Hi Tom,

at the moment, there is no functionality to enable/disable the wiki section for a particular project. We can consider it as a feature request in one of the upcoming releases. Given the way the UI is structured with the dropdown in the main JIRA header that allows browsing for all projects, it would take a fair bit of effort to support this in an intuitive way. 

Could you elaborate a bit more on your particular use-case, so we can better understand?

[Tom Nugter]

Hi Anthony,

Thanks for your answer and my apologies for the late response.

Our use-case is simple: in our JIRA instance we have roughly two kinds of projects; Open source projects and client-related projects. For client-related projects we document information as URL and where to find the code, etc. For these projects the plugin is ideal since the number of people that have access are limited. 

For the open source projects basically everybody access (you need to register though). The technical documentation is done on an external site and the existence of a wiki could, theoretical, mean that documentation could be found here and cause (some) confusion. We have a workaround for now, but the most neat solution would be to disable the wiki functionality for these projects.

Kind regards,

Tom

[Marco Chiarello]

I also have a similar problem. I need to enable a Test Management plugin for a project and another test management plugin for another project. If I Install a plugin it seems it will be available for all the projects, so 2 TM solutions will be available for all the projects. Is there any way to select which plugin is enabled for which project?

Thanks

Marco

[Guillermo Riojas Rodriguez]

 We are facing the same problem whenever we want to test a plugin before rolling it out to the whole company.

We want to avoid creating confusion in development teams, and we want to ensure the plugin fulfills our needs and its worth the investment.

Hopefully administrators could go on each project and activate/deactivate plugins for specific projects. 

[Vinícius Knob]

Hello Anthony, 

Has this feature already been developed? We need it.

Thanks,

Vinícius.

[Deekshith Rao Juvvadi]

Hello Anthony,

Any update on this feature request? This is particularly useful for organizations like ours where the number of projects in a JIRA instance can be huge. 

Thanks,

Deekshith

[Carlos Botero]

Hello everyone. If you are still interested in this, the good news is that there is already a Feature Request in Atlassian's Jira which is currently "Under Consideration".

https://jira.atlassian.com/browse/JRASERVER-59932?_ga=2.250207682.531979720.1573660213-15688529.1557906612

Add your vote to this feature to let know Atlassian that this is something really wanted!

[Vinícius Knob]

Hello Carlos,

I believe the specific issue is https://jira.atlassian.com/browse/JRASERVER-36830.

Thanks for your reply, my team is really interested in that.

Vinícius.

[Carlos Botero]

@Vinícius Knob the issue you shared is marked as "Closed". The one I shared is still active and it is the one that is being currently followed (and the one that should be voted).

https://jira.atlassian.com/browse/JRASERVER-59932?_ga=2.249363651.531979720.1573660213-15688529.1557906612

[Vinícius Knob]

@Carlos Botero, what exactly does the issue JRASERVER-36830 solve? Can I already request to enable/disable plugins for Jira projects? Or I have to wait for JRASERVER-59932?

Thanks,

Vinícius

[binayak.padhy]

Have some one closed already using Classic Software 

How do I disable/enable the plugin for specific projects

May you please help on for the same with the steps

Binayak