On the edit page of a project you can select to 'Enable issue tracker'. But it's an all or nothing option.
Since the Drush project moved to GitHub they also handle issues there. But still users are creating issues on https://www.drupal.org/project/drush
Could we add an option to remove the 'Create a new issue' link from https://www.drupal.org/project/issues/drush?categories=All or set some permission to disallow creating new issues in that queue.
Or maybe a red banner "This issue queue is CLOSED".
When Drush moved I asked to re-open the queue for the sake of having the history accessible.
And with that offered to keep closing new issue there. But it's getting tedious ;)
Comment | File | Size | Author |
---|---|---|---|
#10 | Screenshot 2022-10-10 at 12.02.29.png | 9.9 KB | fjgarlin |
#10 | Screenshot 2022-10-10 at 11.59.35.png | 14.86 KB | fjgarlin |
#3 | project issue options.png | 224.58 KB | jonathan1055 |
Comments
Comment #2
drummI think this could be generally useful for project issue.
Comment #3
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedWe have exactly the same request now that the Devel module has moved to GitLab using the new DrupalSpoons contrib module platform built by Moshe Weitzman. He has automated the migration of all open issues and we have now disabled the issue queue on drupal.org. Individual issues can be found if you know the number, and each Drupalspoon issue has an automatic link added back to d.o. on migration.
However, it would be really helpful if the full issue queue could be viewable and searchable, but no new issues could be added. I have started this question and Moshe agrees that it would be ideal. Other projects may well be moving to DrupalSpoons and this feature would be very good for all of them.
I hope you'll consider adding this option as it will help a large number of d.o. users to stay connected with projects when they move to other platforms.
Comment #4
drummThis setting is actually really incomplete. It doesn’t even prevent new issues from being opened, or moved from a project to one with its issues “disabled.” Relying on this setting isn’t something I can recommend.
Comment #5
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedOK thanks for the info. So is there any hope for the functionality we'd like? If we cannot rely on the existing option is there an alternative? I'm ok with the current option being incomplete. If an occasional new issue is moved to the disabled queue that is manageable. The benefit of generally having the queue viewable but not having a 'Create a new issue' link at the top would be sufficident in 95% of the scenarios and would be a great benefit. There could even be a warning note by the option saying to use it with caution, and explain the short-comings.
Comment #6
drummThat estimate from https://gitlab.com/drupalspoons/devel/-/issues/303#note_350981906 is way off-base.
hook_node_access()
isn’t involved in the current implementation and wouldn’t be added. This is more to do with access to a View.I’d say this is might be a half day of work. Could be closer to a whole day to make the existing setting behave as expected.
You are of course welcome to work on helping to add this.
Comment #7
dwwSee also #524464: Issue node form still works for projects where issues are disabled
We had a lengthy chat in a thread in #drupalspoons on Slack related to this. While the existing checkbox is definitely broken, and while these issues would all be worth fixing, I'm bummed that the "right" fix is to make it highly frustrating and confusing for end users trying to submit issues to projects that have decided to move off site.
Pasting a few of my relevant comments here for history:
Comment #8
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedComment #9
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedIssue #1857390: User can add issues to projects that doesn't have issue tracking enabled. is also working on some inconsistencies and bugs around this.
I suggest showing the list of issues, in case there are any, and also a warning/error message saying that the project is not allowing new ones. The link to add new ones in that view should also disappear in this case.
I suggest that we tackle them together and that we mark this one as a duplicate.
Comment #10
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedActually, the module provides a default value for the view, which I believe is the right one for most cases: to display a 404 page.
This would be the right call in most cases, but for those where it isn't, the view can be altered as needed for the site. See the options available:
These options should be flexible enough to display a message if needed. But as far as the module pre-configured view goes, I think it should stay as it is.
For sites like www.drupal.org, I'd recommend changing the behavior to display the issues. I'll create an issue in that project and propose closing this one.
Comment #11
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedChild issue: #3314448: Show list of issues for a project even if issue tracker is disabled
Comment #12
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedComment #13
fjgarlin CreditAttribution: fjgarlin as a volunteer and at Drupal Association commentedBased on #10, we're closing this issue as the default is just that, a default, but can be altered with the different validators and actions offered.
For the specific case of www.drupal.org, there is this issue #3314448: Show list of issues for a project even if issue tracker is disabled which will allow viewing of the issues with a warning message.