Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.See #69556: move "cvs access" tab into project, make it generic for background. Once that lands, we need a patch to add a 'Maintain issues' checkbox at node/N/maintainers and use that to populate the available options for the Assigned dropdown.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 880820-6.project_issue_maintainer.patch | 6.59 KB | dww |
| #6 | 880820-6.project_issue_maintainer.interdiff.txt | 4.19 KB | dww |
| #4 | 880820-3.project_issue_maintainer.patch | 6.7 KB | dww |
| #1 | 880820-1.project_issue_maintainer.patch | 7.83 KB | dww |
Comments
Comment #1
dwwComment #2
mikey_p commentedSeems like ideally there'd be a separate permission for 'administer project issues' allowing them access to node/$pid/edit/issues?
Edit: While this may be true, there are some other sticky issues here with controlling access to the primary Edit tab and whether or not it would be visible if the project edit tab is not visible...might have to try this out and see what happens.
Comment #3
mikey_p commentedHere's an example of what I was trying to describe:
Comment #4
dwwRerolled #1 based on the latest API changes over at #69556-30: move "cvs access" tab into project, make it generic.
mikey_p and I talked about an 'administer project issues' perm in IRC. Summary: let's not add that unless we actually need it. For now, we'll just say you have to be able to edit the project node to change those issue-related settings. It's cool we've got a flexible system now, but let's not go crazy making it extra granular if there's no real need for it.
Comment #5
dwwRe: #3: No, that tab won't be visible. But, the direct links to those pages still work. Try it yourself. ;) If you give a user just 'administer project releases' perm, but not 'administer project' perm, the "Administer releases" link on the project page, which sends you to node/N/edit/releases still works and the page renders. And you see the "View" tab. But no Edit tab and no subtabs for issues and releases.
Comment #6
dwwNew patch based on #69556-43: move "cvs access" tab into project, make it generic
Comment #7
dwwBoth sun and wonder95 don't like "Maintain issues", and both proposed "Assign issues" instead. Anyone can still assign issues to themselves. So, it's a bit misleading. It really means "Assign issues to anyone else with this permission". That's why I thought "Maintain issues" was good -- you're an issue maintainer. And, it's possible we'd dream up some other powers we'd give to people with this. But, I'm open to a better suggestion if anyone's got one.
Comment #8
sunHm. "Assign issues to anyone else with this permission" actually is what I'd understand for "Assign issues" - otherwise, I'd expect the label "Be assigned to issues" :)
Comment #9
dwwBojhan reviewed and thought "Maintain issues" was actually fine for this, so I'm going to leave it like that for now.
Comment #10
dwwCommitted, merged into bzr, deployed on d.o. DB updates ran without error. Hurray!