summaryrefslogtreecommitdiff
path: root/app/models/project_feature.rb
diff options
context:
space:
mode:
authorZ.J. van de Weg <git@zjvandeweg.nl>2016-11-12 11:17:24 +0100
committerZ.J. van de Weg <git@zjvandeweg.nl>2016-11-17 21:34:23 +0100
commit9d8ca60d221a1500e31ef05ecf8c4db56adde3c0 (patch)
tree5993d391ca0bb484829f7d3f49a1948bb6f85a41 /app/models/project_feature.rb
parentc2e6f5fc241b3a3bc980dfbdaf9af6c59a098af5 (diff)
downloadgitlab-ce-9d8ca60d221a1500e31ef05ecf8c4db56adde3c0.tar.gz
issue and mergerequest slash command for mattermost
This commit includes a couple of thing: - A chatops controller - Mattermost::CommandService - Mattermost::Commands::(IssueService|MergeRequestService) The controller is the point where mattermost, and later slack will have to fire their payload to. This in turn will execute the CommandService. Thats where the authentication and authorization should happen. So far this is not yet implemented. This should happen in later commits. Per subcommand, in case of `/gitlab issue show 123` issue whould be the subcommand, there is a service to parse the data, and fetch the resource. The resource is passed back to the CommandService which structures the data.
Diffstat (limited to 'app/models/project_feature.rb')
-rw-r--r--app/models/project_feature.rb4
1 files changed, 4 insertions, 0 deletions
diff --git a/app/models/project_feature.rb b/app/models/project_feature.rb
index 5c53c8f1ee5..03194fc2141 100644
--- a/app/models/project_feature.rb
+++ b/app/models/project_feature.rb
@@ -60,6 +60,10 @@ class ProjectFeature < ActiveRecord::Base
merge_requests_access_level > DISABLED
end
+ def issues_enabled?
+ issues_access_level > DISABLED
+ end
+
private
# Validates builds and merge requests access level