Skip to content

Scrap dangerous and hard to support features #361

Description

@MrBunsy

Up for some discussion, but I see no reason to keep the following:

  • Manage Metadata Fields. I can see no reason you'd ever want to add a field via the web GUI. You can't really make use of it without editing a lot of other things (citations, actual code, templates, workflows, rendering)
  • View config. If we had a "real" configuration system that actually presented all fields all plugins required configuring (ala Jenkins). I'd understand this. Instead we've given admins enough rope to shoot themselves.

And I think it's worth considering scrapping these, but am open to persuasion:

Any features we support need testing, and need customers supporting. The fewer the features, the less work!

Metadata

Metadata

Assignees

Labels

investigationInvestigate how something works/behaves

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions