>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3427961. --> Reported by: [drumm](https://www.drupal.org/user/3064) Related to !328 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Drupal.org has multiple statuses for closed issues: fixed, duplicate, works as designed, etc. GitLab issues only have the boolean open/closed built in. More metadata can be added to record the reason for closing, but that does not have to be standard per-project. A maintainer could add Closed-reason:bad-idea if they like. <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/infrastructure/issues/3254602" title="Status: Needs review">#3254602: Using GitLab labels for issues on Drupal projects</a></span> is the issue for planning standard label use.</p> <p>Currently, issue credit is only awarded for fixed issues. Credit is meant to encourage productive contributions. Fixed issues are more likely to have been helpful. Maintainers don&rsquo;t have to think about giving credit for issues that are works as designed, outdated, or any other closed, not fixed status. The maintainer&rsquo;s crediting checkboxes do always save who would be credited, but the credit is not awarded unless the issue gets fixed.</p> <p>In addition to GitLab not having the same statuses, there are legitimate cases where an issue that doesn&rsquo;t get fixed, but still needed non-trivial effort. An outdated issue might have required quite a bit of research to confirm the issue is no longer present. Right now, if the maintainer does think that effort should be credited, they would have to shoehorn it into fixed status.</p> <p>Before we start migrations for rebuilding issue crediting <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-1"><a href="https://www.drupal.org/project/infrastructure/issues/3322116" title="Status: Active">#3322116: Contribution records revamp</a></span>, we can make the existing issue credit system act like the future system. This will get maintainers used to being able to credit anything closed; as always, they should not feel obligated to credit unproductive issues &amp; comments. And there will be less changing at launch time.</p> <h3>Potential solutions</h3> <ul> <li>Stay as-is, with a group-level label for &ldquo;Fixed&rdquo; in GitLab. Displays of issues credited will only show issues that are both closed and have the fixed label. If maintainers use some other label, that won&rsquo;t be credited. Maintainers can not remove the &ldquo;Fixed&rdquo; label option. </li><li>Credit is possible for all closed issues. We embrace GitLab&rsquo;s flexibility, maintainers don&rsquo;t need to use any labels, unless they want to. Recording credit for any closed issue that required non-trivial effort is encouraged. </li></ul> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-8"><a href="https://www.drupal.org/project/infrastructure/issues/3254602" title="Status: Needs review">#3254602: Using GitLab labels for issues on Drupal projects</a></span> is moving toward not requiring standardized labels. Credit will be possible for all closed issues.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>If this moves forward, any credit-related place which looks for Fixed &amp; Closed (fixed) issues would be replaced with <code>not in project_issue_open_states() or Fixed</code>. This includes a few places in module code and Views filters.</p> <p>Since potential credit previously recorded would be awarded, likely without the maintainer knowing, all closed not-fixed issues should be bulk updated to remove that record.</p> <p>Documentation should be updated, maintainers should be given explicit allowance to use their judgement and not feel obligated to record more credit for all types of closed issues. They should continue crediting productive contributions, and now have more options to do so.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>The UI should reflect the changes.</p> > Related issue: [Issue #3254602](https://www.drupal.org/node/3254602) > Related issue: [Issue #3322116](https://www.drupal.org/node/3322116) > Related issue: [Issue #3432188](https://www.drupal.org/node/3432188) > Related issue: [Issue #3227737](https://www.drupal.org/node/3227737)