Add credit award date and weighting to feed

Created on 29 July 2025, 19 days ago

Problem/Motivation

This new tool looks great.

At Zoocha we incentivise our devs to earn credits in their spare time. Knowing the date the credit was awarded is important for that process. You can't rely on the updated date of the issue as this can change after the credit has been awarded, sometimes months afterwards.

It would be nice to know how many credits were actually earned too, with core and other initiatives weighted.

Providing this information would further help assist the company to contribute more to Drupal.

Steps to reproduce

Here's my own personal feed for Zoocha.

http://new.drupal.org/contribution-records-by-organization-by-user?usern...

There's no date or weighting in there, which would allow any automation of our internal credit tracking.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

✨ Feature request
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom dunx

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

Comments & Activities

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

    The information is already there. The field that you are interested in is: field_last_status_change

    That field is updated when the record is marked as "Fixed".

  • πŸ‡ͺπŸ‡ΈSpain fjgarlin

    That's the field we use when querying "last 3 months" or "last year" for issues.

  • πŸ‡¬πŸ‡§United Kingdom dunx

    Nice one thanks.
    Shall I raise a separate ticket for the weighting part?

  • πŸ‡ͺπŸ‡ΈSpain fjgarlin

    It would be nice to know how many credits were actually earned too, with core and other initiatives weighted.

    That's something that can only be checked in the "Owner tools" of each organization.

    The code and some of the weighting is linked here: https://www.drupal.org/drupalorg/docs/marketplace/contribution-credit-we... β†’

    But individual issues/records does not carry that weight information. A record is a record, whether it is from core or any module, and then later on, our marketplace tooling applies the weight depending on the project.

    So, it's not possible to expose individual weighting information.

  • πŸ‡¬πŸ‡§United Kingdom dunx

    Separate system. Understood. Thanks for the info.

  • πŸ‡¬πŸ‡§United Kingdom dunx

    Hi. We've worked through this and the field_last_status_change does not match the date the credit was awarded.

    Having a single credit awarded/earned/applied/recognised date is crucial for those partners wanting to accurately incentivise staff for earning credits within a calendar month. Without it, credits can be recorded for an individual within the month it was earned and the month the issue was marked as 'Closed (fixed)' (assuming that date will never get changed again after this final status change) unless we do a heap of manual cross-checking of issues against credits already attributed.

    As the feed doesn't seem to include the issue status, it's not possible to create logic to lock down the award of a credit to a single point in time, i.e. the month the status changed to 'Closed (fixed)'.

    As an example, the field_last_status_change is 10 July 2025 for dunx on issue https://www.drupal.org/project/project_browser/issues/3497651 πŸ› Ally issues for Project Browser in gin dark mode Active , which is the date the issue was automatically closed. I was awarded that credit on 26 June as shown in the issue screenshot.

    Could this feature request be re-opened as we would still very much like to be able to determine a single date for credit award within this really useful feed?

  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

    Any closed status for the issue, including Fixed, will award credit. It is not limited to Closed (fixed).

    If an issue is updated to re-open, fixed again, etc, the last status change, is indeed reset and the amount of time the attributed credit is considered for Drupal Certified Partner programs and ranking is also reset. There is not a single point in time that the issue is closed.

  • πŸ‡¬πŸ‡§United Kingdom dunx

    Thanks for that additional information, which actually makes the situation worse for our purposes. That could even be manipulated to maintain credits within the last 3 or 12 months.

    There is a single immutable point in time when the contribution credit is awarded and, as this is the contribution record feed, I am requesting a feature where that time is provided as part of the feed... and no problem if the answer is 'we can't/won't provide that'. That would make this feed really useful for our purposes and possibly others as we aim to turn more takers in to makers.

  • πŸ‡ΊπŸ‡ΈUnited States drumm NY, US

    Sorry, that is not something we plan to track, since it would not be used in Drupal Certified Partner programs and ranking.

Production build 0.71.5 2024