When using an external issue tracker, Trident must not be able to create GitLab issues

I'm self hosting GitLab and we're using Redmine as an external issue tracker. Therefore the issue creation is disabled in our GitLab web interface.

However, trident allows creation of GitLab issues anyways. This must not be! Trident must be aware of external issue frackers and disable issue creation or hide the whole issues tab!

Reassigned to @Freshcocoa

Milestone changed to Version 1.1

Added Feature Request label

mentioned in issue #31 (closed)

I would rather label this as a bug and not as a feature request. Users shouldn't be allowed to use this when an external issue tracker is defined!

Also you cannot close or delete issues in the trident app when created through the app. Don't know if this is related to this issue or a global bug...

Milestone changed to Version 1.0 Public Release

Added Bug and removed Feature Request labels

Looking closer to this, agreed Tobias, thank you.

Should be fixed in the next build

Status changed to closed

Status changed to reopened

@Freshcocoa I'm very sorry, but in build 82 I am still able to open a new issue, despite I have an external tracker enabled.... For those issues, the "Close issue" button still won't work. It changes to red "Reopen issue" but as soon as I go back to the Issues View, it appears as open.

Hey Tobias, oops! Good job you noticed that.

In the project API there is an 'issues_enabled' flag on the project. If this is set to false, it should disable the entire Issues tab (see attached). This was included in build 82, I wonder if there's something else about the project settings that also indicates external trackers?

Are you using these settings?

oh, okay, so we spoke about different things... ;-)

yes, you can either enable or disable Issues via the "issues enabled" option. But you can also define/enable an external issue tracker in project settings > Services > {Jira, Redmine, etc.}. This will, however, only work when you have the "Issue" feature enabled.

So my setting is:

• Project settings > Features > Issues "enabled"
• Project > Services > Redmine "activated"

And via the web interface I cannot use the built in GitLab issue tracker. It will always redirect to my redmine installation. also issue links like #424 will link to Redmine then and not to the internal issues. I'm not able to use the built in GitLab issue tracker, but Trident lets me use it...

I can't see anything in the Gitlab REST API that shows how one can query if an external tracker is being used :(

What a bummer... :-(

I reported this issue in gitlab-org/gitlab-ce#2825

Going to move it into the backlog until we find out more on the issue.

Milestone changed to Backlog

I checked this out and it seems it's not available on the projects endpoint but you can find it out.

https://github.com/gitlabhq/gitlabhq/blob/master/doc/api/services.md#get-custom-issue-tracker-service-settings

This endpoint returns something like this when not enabled, when enabled the active attribute is set to true.

{
   "id": 538,
   "title": "Custom Issue Tracker",
   "project_id": 182,
   "created_at": "2015-09-11T13:20:43.000+02:00",
   "updated_at": "2015-09-11T13:20:43.000+02:00",
   "active": false,
   "properties": {},
   "template": false,
   "push_events": true,
   "issues_events": true,
   "merge_requests_events": true,
   "tag_push_events": true,
   "note_events": true
}

So the issues tab also needs to be hidden or show a button to the external issue tracker (which is a attribute called issues_url in properties).

{
    "id": 538,
    "title": "Pizza",
    "project_id": 182,
    "created_at": "2015-09-11T13:20:43.000+02:00",
    "updated_at": "2015-09-29T13:05:34.000+02:00",
    "active": true,
    "properties": {
        "title": "Issues",
        "project_url": "http://issues",
        "description": "Custom issue tracker",
        "issues_url": "http://issues.all",
        "new_issue_url": "http://issues.new"
    },
    "template": false,
    "push_events": true,
    "issues_events": true,
    "merge_requests_events": true,
    "tag_push_events": true,
    "note_events": true
}

Thanks for investigating this, @stayallive

Oops sorry for the delay getting back on this, been very busy updating the website!

Reopened this issue, thanks for finding a solution to it @stayallive !

Milestone changed to Version 1.0 Public Release

Build #83 (closed) should fix it:

If a project has a properties hash, which contains a url in issues_url, then an external issue tracker is assumed to be used.

@Freshcocoa I'm afraid it still don't work... :-(

Matt, I just created you an account in our organizations GitLab and added you to a test repo with external issue tracker enabled. This is probably the best way to test and sort things out...

JSON from a project that has custom tracker

{
	"id": 468,
	"title": "Custom Issue Tracker",
	"project_id": 24,
	"created_at": "2015-09-30T07:18:45.929Z",
	"updated_at": "2015-09-30T07:18:45.929Z",
	"active": false,
	"properties": {},
	"template": false,
	"push_events": true,
	"issues_events": true,
	"merge_requests_events": true,
	"tag_push_events": true,
	"note_events": true
}

JSON from project that doesn't have a custom tracker

{
	"id": 550,
	"title": "Custom Issue Tracker",
	"project_id": 49,
	"created_at": "2015-09-28T12:00:58.848Z",
	"updated_at": "2015-09-28T12:00:58.848Z",
	"active": false,
	"properties": {},
	"template": false,
	"push_events": true,
	"issues_events": true,
	"merge_requests_events": true,
	"tag_push_events": true,
	"note_events": true
}

Milestone changed to Version 1.1

Does anyone know if the API is updated yet to support this?

@matthew.wilkinson did you check the demo repository on my server? Does it expose anything you can use?

@tofi86 +1

Milestone changed to Version 1.3

Reassigned to @matthew.wilkinson

Milestone changed to Backlog