Allow projects to have multiple issue tracker services
Dev: https://dev.gitlab.org/gitlab/gitlabhq/issues/2142
Allow projects to have multiple issue tracker services, with a primary one and secondary ones identified by prefixes. In the case of GitLab.com, we could have these four:
-
#123
- GitLab itself -
#GH-123
- https://github.com/gitlabhq/gitlabhq -
#DEV-123
- https://dev.gitlab.org/gitlab/gitlabhq -
#FORUM-123
- https://forum.gitlab.com On dev.gitlab.com we could have: -
#ZENDESK-123
- https://gitlab.zendesk.com -
#COM-123
- https://gitlab.com/gitlab-org/gitlab-ce
This would be useful for any customer that uses multiple tracking systems e.g. Zendesk
We'd have to see how this interferes with current JIRA #PROJECT-123
links, but I think that'll be easy enough to work around.
A next step would be to make the JIRA issue cross referencing that's in EE a bit more generic and implement that for more services. An automatic note on Zendesk when a ticket is referenced in an issue would be really cool, but that's not currently feasible because no-one wants to replace GitLab issues by Zendesk entirely.
Douwe
In response to @dzaporozhets in https://dev.gitlab.org/gitlab/organization/issues/159:
I think the best option is just using full urls. All this DEV-123 reminds me of JIRA which is not good sign.
I don't like that the full links can only be copy-pasted and not by hand, that they break the flow of a sentence more than a simple
As I mentioned in issue #DEV-123, X, Y and Z
and that they (currently) can't cross-link to the referenced issue. I'm also not sure how "reminding of JIRA" is bad per se?#DEV-2142
is shorter thanhttps://dev.gitlab.org/gitlab/gitlabhq/issues/2142
, which is something JIRA realized as well, but otherwise it has nothing to do with them.
Dmitriy
You can copy paste full urls. I am not going to type DEV-123 every time. Its annoying.
Douwe
How is typing
#DEV-123
more annoying than typing#123
or!123
to reference issues/MRs on the current issue tracker? We don't copy-paste links for those. I don't understand how typing#DEV-123
is more annoying than copy-pasting the full URL. If copy-pasting the full URL is easier than typing the number manually, why do we have#
and!
at all? It simplifies finding references in text, but if most users preferred copy-paste to writing manually, we and GH etc would have supported that from the start.
My main issue with full URLs is that it breaks the flow of the sentence, and I really like the "short hand" reference notation because of how it reads and because it doesn't require context switch with address bar etc to write. I don't see why we would support that for the current issue tracker, but not external ones.
Sytse
Maybe we can paste a full URL and have GitLab show it shortened? But first step would be to properly crosslink when pasting a full url. [ALREADY DONE]
Dmitriy
How is typing #DEV-123 more annoying than typing gitlab-ee#123 or gitlab-ee!123 to reference issues/MRs on the current issue tracker?
typing gitlab-ee#123 gives me autocomplete. and I also usually copy-paste id from URL. And I dont need to remember shortcuts like DEV, ZENDESK