[feature] Ability to enable/disable wiki system and issue tracking for all repositories

[kumlali]

• Gitea version (or commit ref): 1.3.2
• Git version: 2.9.3
• Operating system: Red Hat Enterprise Linux Server release 7.4
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • [x ] SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (provide example URL)
  • No
  • [x ] Not relevant
• Log gist:

Description

It would be nice to have a configuration option that allows administrators to enable and disable wiki system and issue tracking of all repositories.

I could manage to disable issue tracking(not wiki system) of all the repositories by executing following SQL statements:

DELETE FROM repo_unit WHERE type=2;
UPDATE repo_unit SET config='{}';

P.S.: Similar request for Gogs: gogs/gogs#3738

[coreyjewett]

I was hoping to disable wikis system wide, but using an entry in the ini configuration.

[lunny]

That's not very difficult.

[ve3]

enable/disable pull request system wide please.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[jpicht]

I am currently working on implementing this over here. It is currently work in progress, but I hope to finish it tomorrow.

[tech-alchemist]

Any hope? or shud we click fork ? 😯

[jolheiser]

The above referenced PR has had activity within the last few days.

[davidsvantesson]

There seem to be need of some discussion and consensus on what this feature exactly shall do. Most of the use-cases can be handled by scripts using the API and/or template adoptions, but that is not very user-friendly for a common case.

I would like to see the repo units as different features (buildin or plugins) of Gitea that should be possible to install and uninstall (if it is included in the gitea executable is not important here). It should also be possible to select which features (units) are default for new repositories. What should happen if you "uninstall" a unit, shall all data be removed? And the same if you "install", shall it be default be added on existing repositories. To handle that option and be able to give warnings, the install/uninstall procedure should preferable be in the admin UI rather than in app.ini.

If plugin system and site configuration storage needs to be discussed for this issue, I'm afraid it will take some time before it can be merged.

[davidsvantesson]

As proposed by @6543 lets have a vote on the different options. Sorry for the many options, I found quite many possibilites to solve this.
Read Delete all as Disable unit for all repos .

Delete means to delete/disable the unit setting so it has to be manually enabled again, not the content of issues etc. Enable all means it the unit is globally enabled again, it will be enabled on all repositories if it is a default unit. In the last option, repositories created while the unit was disabled will have it if enabled again.