#501 Anitya does not grand a badge
Closed: duplicate 4 years ago Opened 4 years ago by zdenek.

Problem:
I added several projects in Anitya (https://release-monitoring.org/) but the Telegraphist badge (https://badges.fedoraproject.org/badge/telegraphist-upstream-release-monitoring-i) wasn't granted.
As I can see, last one was granted on 30th September and nothing else since that time (I'm sure more people fulfilled the badge requirement since that time).
Infra team confirmed, they can see the fedmsg messages... but the badge didn't fire off.

This issue was opened in Pagure as well (https://pagure.io/fedora-badges/issue/4). Because I do not know which of these two ticketing tools is preferred, I opened this issue here as well and added link to the second tool.


Did anyone check this issue please?

Metadata Update from @zdenek:
- Issue close_status updated to: None

4 years ago

Metadata Update from @sayanchowdhury:
- Issue assigned to sayanchowdhury

4 years ago

Can you move the issue to https://github.com/fedora-infra/tahrir ?

Metadata Update from @sayanchowdhury:
- Custom field concept_review_passed reset (from 0)
- Custom field has_description reset (from 0)
- Custom field has_name reset (from 0)
- Custom field needs_manual_award reset (from 0)
- Custom field triaged reset (from 0)

4 years ago

Done, please see issue 364 (https://github.com/fedora-infra/tahrir/issues/364)
Many thanks for your support!

Metadata Update from @sayanchowdhury:
- Custom field artwork adjusted to has_concept
- Custom field concept_review_passed adjusted to passed (was: false)
- Custom field has_complete_yaml reset (from None)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue tagged with: bug

4 years ago

See upstream ticket

Closing this ticket as duplicate, as the discussion as moved to the upstream project where this is a problem.

Metadata Update from @jflory7:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)

4 years ago

Metadata Update from @jflory7:
- Custom field has_complete_yaml reset (from false)
- Custom field has_description reset (from false)
- Custom field has_name reset (from false)
- Custom field needs_manual_award reset (from false)
- Custom field triaged reset (from false)
- Issue close_status updated to: duplicate
- Issue priority set to: no deadline
- Issue status updated to: Closed (was: Open)

4 years ago

Are we sure the rule is correct, here? The Telegraphist rule triggers on topic anitya.project.map.new, but I only see messages if I search for topic org.release-monitoring.prod.anitya.project.map.new instead.

Login to comment on this ticket.

Metadata