Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Some projects, like drush were initially managed via drupal.org but then moved their issue queues to an external platform.
The problem is, that if you untick "Enable issue tracker", then the whole view of past issues disappears, which shouldn't.
Steps to reproduce
Disable issue tracker in a project with issues, then go to the issue listing page for that project, you get a 404 page.
Proposed resolution
To still show the issues, but also display a message warning users that the issue tracker is no longer in use, and make sure that there are no links to add new issues within the views.
Update: the second part of the suggested resolution is done by the "project_issue" module in this issue #1857390: User can add issues to projects that doesn't have issue tracking enabled.
Remaining tasks
Create a MR with the changes.
Issue fork drupalorg-3314448
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
fjgarlin commentedComment #4
fjgarlin commentedChanged the validator so the issue listing still shows.
Improvements in other issues like #3314430: Render link to issues only if issue tracker is enabled, #1857390: User can add issues to projects that doesn't have issue tracking enabled. and a few other will also add warning messages, remove links when the tracker is disabled, etc.
Comment #5
fjgarlin commentedComment #6
fjgarlin commentedTesting instructions here: https://www.drupal.org/project/project_issue/issues/1857390#comment-1473...
Comment #9
drummLooks good, merged.
Comment #10
jonathan1055 commentedThanks for working on this. Just for my info, you have committed this to 7.x-3.x but we need to wait for the next tagged release to be availbale and in use on drupal.org? Or is it live already?
Comment #11
fjgarlin commentedYou might have already found out, it's live. ie: https://www.drupal.org/project/issues/devel
Comment #12
jonathan1055 commentedThanks fjgarlin, yes it was Devel that I was interested in. That's great. So we can add a link manually to the existing issue queue from the project page, but no new issues can be created. Interesting that there has been around 10 new Devel issues created on druopal.org since Moshe migrated the issue queue and disabled it in May 2020. Good to have this bug fixed. Thank you to you and drumm.
Comment #13
fjgarlin commentedYeah, there were some related issues (ie: #1857390: User can add issues to projects that doesn't have issue tracking enabled.) where you could also move issues to projects where issues were disabled. This should be fixed too already.
Comment #14
jonathan1055 commentedYes it is fixed. I was following those too.
Comment #15
drummRight, I had mentioned specifically that the disabling issue queue functionality was broken, but we didn’t get much help in improving it. We’ll be using this to migrate issues to git.drupalcode.org, which is why it got done now.
For now, issues will always be on for every project on git.drupalcode.org, once we’ve migrated them. The option to disable them is intermingled with other project-level settings in GitLab, and there isn’t functionality to expose just that option.