I can't save contribution records for a project I maintain

Created on 14 August 2025, about 1 month ago

Problem/Motivation

I co-maintain the Sitemap module β†’ .

For some recent issues, I saw the new "Preview the new Contribution record" button when I was ready to commit, so I tried using it, and it appears to have created some contribution records.

After checking contributors in the new contribution record, I didn't see a "Save" button to save my changes; and when I reload the page, the contributors I had checked are unchecked again. Furthermore, I don't see the issue listed on the contributor's user page (i.e.: @jernejmramor β†’ should now have credit for πŸ› Vocabulary plugin stops outputting items in complex hierarchical vocab Active but doesn't)

(for what it's worth, I also used the new commit message format, and marked the issue as "Fixed")

Steps to reproduce

  1. Log in as @mparker17 on [old.]drupal.org and new.drupal.org
  2. Create an issue in a project you maintain on [old.]drupal.org
  3. Create an issue fork on [old.]drupal.org and push code to it
  4. Create a merge request from the issue fork on git.drupalcode.org
  5. Move the issue to "Needs review" on [old.]drupal.org
  6. Move the issue to "Reviewed & tested by the community" on [old.]drupal.org
  7. On [old.]drupal.org, Click the "Preview the new [Contribution record]" button between the "Files" details element and the "Credit & committing" details element.
  8. You are taken to new.drupal.org. Check contributors to give them credit...
    • Expected behavior: I see a Save button at the bottom of the Contribution Record page
    • Actual behavior: I don't see a Save button at the bottom of the Contribution Record page

    (note: I expect to see a Save button based on the screenshots from the announcement post β†’ )

  9. On new.drupal.org, copy the commit message from the new Contribution records page
  10. Go to the merge request on git.drupalcode.org... in the "Ready to merge" section, check "Edit commit message", and paste the commit message from the new Contribution records page. Then click "Merge"
  11. Wait for the merge train to finish
  12. Go back to the issue on [old.]drupal.org; you see a new "mparker17 committed HASH on BRANCH" commit
  13. On [old.]drupal.org, move the issue to fixed
  14. On [old.]drupal.org, click the "Preview the new [Contribution record]" button
    • Expected behavior: The contributors I checked earlier are still checked
    • Actual behavior: The contributors I checked earlier are not checked
  15. Go to the user account pages of the users I checked earlier
    • Expected behavior: The contributors get credit for the issue on their user account pages
    • Actual behavior: The contributors do not yet have credit for the issue on their user account pages

Proposed resolution

Not sure!

I suspect I don't have permission to save contribution records. I'm happy to help test. These days I'm most active on the Sitemap β†’ and Elasticsearch Connector β†’ projects β€” in both cases, I'm a co-maintainer, not the author/original-maintainer (if you'd like I can test on a project that I am the author/original-maintainer of).

Remaining tasks

Not sure!

User interface changes

From the announcement post β†’ , I assume I should see a "Save" button on the new Contribution records page.

API changes

To be determined!

Data model changes

To be determined!

πŸ› Bug report
Status

Active

Version

1.0

Component

User interface

Created by

πŸ‡¨πŸ‡¦Canada mparker17 UTC-4

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mparker17
  • πŸ‡ͺπŸ‡ΈSpain fjgarlin

    8. We are opening the new UI as read-only during a few weeks so people get used to it. You need to still save the credits on the issue page for now. We will enable saving on the new UI (and disable in the old) within the next 2 weeks (expected).

    15. We are caching these credit blocks for 1h, so it’ll take time to show up after the issue is closed.

Production build 0.71.5 2024