Afaik in GitLab Wiki you can mention issues to link to them (same as in merge requests and elsewhere). Is that what you had in mind or is the integration in Confluence deeper?

The JIRA <-> Stash integration is also nice. Create a bug in JIRA and reference a release tag (which integrates with Stash), create a branch to fix it right from the ticket, ticket shows when that branch gets a PR and is eventually merged. It's possible to e.g. close the ticket when the bug fix gets merged too.

It does work in redmine[1] and that for years and the same as in github and Jira, using the #XXXX notation.

[1]: http://www.redmine.org/projects/redmine/wiki/RedmineTextForm...

That does not let me create something from the wiki, only reference issues that already exist.

EDIT:

Specifically, allowing people who are primarily text driven to be reading a doc/wiki page, right click a sentence or phrase, then create an issue right from that screen, without leaving, and have them linked back and forth, is... seemingly obvious, yet I've not seen it done elsewhere. Someone else pointed out gitlab - I've not tried it there yet.

There IS a Add-on for exactly that use case: https://marketplace.atlassian.com/plugins/net.seibertmedia.c...

Disclaimer: I work for the Add-on developer

For redmine?

The creation of jira tickets from confluence already seemed useful enough for my use cases - not sure that I'd need a plugin to do more, but interesting to see that you've got something (and to know others want it).

My original post was pointing out that this wiki/ticket connection is something I've only ever seen in jira/confluence, not in anything else.

Phabricator has the wiki, code review, and ticketing systems tightly integrated. It's a clean, fast, and free alternative to JIRA.

https://www.phacility.com

I'm a long time JIRA user who started using Phabricator last year for a side project (that has now become my main project).

I didn't really have a major problem with JIRA, but we self hosted them on AWS, and the resource requirements of JIRA, Confluence, Fisheye etc. meant that we had to set up separate instances to stop them crashing all the time.

Phabricator gives us the same functionality as all the Atlassian tools I mentioned above, but on one virtual Digital Ocean $10/mo server. It is much more reliable, and has a better, much more integrated UI.

Faster too - MUCH faster. I can really tell when I go back to JIRA to log a bug and have to wait 5 to 10 seconds for a form to build itself and load.

What the hell are people doing to their Jira instances that make them load that slowly? I've got a fairly busy instance at $dayJob with hundreds of users, 10+ addons, and some automation scripting, and it runs as fast as any webapp can be expected to.

There was no explicit performance tuning happening here, either. 1 instance of Jira talking to 1 instance of MySQL behind 1 instance of nginx on a modest VM.

I'm not doubting you, but this is a common enough complaint that I assume there's a footgun lying around that I've managed to luckily step over.

I dunno, but the hosted version has (imo) always been rather slow. It's felt faster in the last year or so, but definitely slower than most other tools I use (mostly redmine these days when not in jira).

The FogBugz project management system has pretty good integration between its case system and its wikis.