- Issue created by @apaderno
- š®š¹Italy apaderno Brescia, š®š¹
It happened again today: Attribute to organizations or customers was not selected in the credit record pages for issues I edited, except for one.
All the issues I edited, and for which I checked the credit record page to credit people who should have been credited, were old issues, but that should not make any difference.
- š®š¹Italy apaderno Brescia, š®š¹
In an issue, neither Iām volunteering my own time nor Attribute to organizations or customers was selected, despite I always select Iām volunteering my own time and deselect Attribute to organizations or customers, and click on Save and set as default, when a credit record page shows as selected the wrong values.
- š®š¹Italy apaderno Brescia, š®š¹
As last note: The credit record pages for closed issues started to show both Attribute to organizations or customers and Iām volunteering my own time selected; the same happens for this issue.
I commented on š¬ Offering to co-maintain User restrictions Active , where I have not posted any other comment. When I visited https://new.drupal.org/contribution-record/10009527, I still got both Attribute to organizations or customers and Iām volunteering my own time selected.
It seems the value I set as default are not saved as such.
- šŖšøSpain fjgarlin
...were old issues, but that should not make any difference.
There is a difference with new issues vs old issues where you already are part of it. The setting should persist for brand new issues and new attributions.
But if you were already listed on an issue before September 3td, which is when we did the change, the value for that checkbox is the value that was set in the D7 issue.
We only use defaults when we are bringing a user for the first time into an issue.
I will close it with "Cannot reproduce", but if you notice this in new issues and new attributions, please reopen.
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.
- š®š¹Italy apaderno Brescia, š®š¹
We only use defaults when we are bringing a user for the first time into an issue.
On š¬ Offering to co-maintain User restrictions Active , I posted for the first time on September 7, 2025. Still, after I posted that comment, https://new.drupal.org/contribution-record/10009527 did not show my default values.
The last screenshot in my previous comment shows what I saw. - š®š¹Italy apaderno Brescia, š®š¹
if you notice this in new issues and new attributions, please reopen
The same happened on š Add acbramley as co maintainer Active : I edited the issue metadata today, and visited https://new.drupal.org/contribution-record/11423535. Still, the form shows as selected two options instead of one.
If I change the values shown for that issue, and click on Save and set as default, those values will be remembered for that issue, but for a new issue where I post my first comment, those values are not remembered, which means the Save and set as default button works like the Save button.
- šŖšøSpain fjgarlin
I think I found the issue. This commit shoudl fix it: https://git.drupalcode.org/project/contribution_records/-/commit/61cd04e...
- šŖšøSpain fjgarlin
This is deployed and should be fixed now. No need to resave defaults, it should just pick them up properly.
Now that this issue is closed, please review the contribution record.
As a contributor, attribute any organization helped you, or if you volunteered your own time.
Maintainers, please credit people who helped resolve this issue.