Namespace license checks for issue weights

Related to https://gitlab.com/gitlab-org/gitlab-ee/issues/2335

Set weight of issues (EES / Bronze)

1. Do not display Weight option when creating or editing an issue.

Introduced in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/76 by @dzaporozhets

mentioned in issue #2335 (closed)

assigned to @nick.thomas

mentioned in merge request !2291 (merged)

@DouweM do we want to exclude issue weights from the filtered search input as well? That's frontend / JS-heavy, but I can dig into it.

I assume we also don't want it to appear on the issue show page, as well as edit and new.

Issue weight is also used in:

• sorting
• burndown charts
• slash commands
• milestones
• api

Rather than fiddling with the filtered_search JS, it's probably enough to not return issue weights in search results, and not to respect issue weights in the search query.

Following discussion with @DouweM, we're going to make burndown charts feature depend on both the burndown_charts and issuable_weights license feature. If we ever sell a plan that includes the former and not the latter, we can work on making burndown charts work without issue weights then.

Group milestones show a "total issue weight", which is currently an efficient database lookup. I'll need to come back to how best to restrict this.

closed via merge request !2291 (merged)