Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Task]: Unlisted add-on versions should not affect the last updated field #15274

Open
1 task
abyrne-moz opened this issue Jan 9, 2025 · 0 comments
Open
1 task

[Task]: Unlisted add-on versions should not affect the last updated field #15274

abyrne-moz opened this issue Jan 9, 2025 · 0 comments
Labels
repository:addons-server Issue relating to addons-server

Comments

@abyrne-moz
Copy link

abyrne-moz commented Jan 9, 2025 •
edited by data-sync-user
Loading

Description

Currently, the last updated field of an add-on is updated when a new unlisted version is uploaded. This causes the AMO searches to be misleading when sorting by the last updated field.

Whilst this field is also used in the developer hub, the audience for this is smaller than those who search on AMO. In future, we will look at using a different field for the developer hub updated information.

Acceptance Criteria

Milestones/checkpoints
Preview Give feedback

Checks

  • If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task
@abyrne-moz abyrne-moz added needs:info repository:addons-server Issue relating to addons-server labels Jan 9, 2025
@abyrne-moz abyrne-moz changed the title [Task]: Unlisted add-on versions should not affect the last updated fied [Task]: Unlisted add-on versions should not affect the last updated field Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
repository:addons-server Issue relating to addons-server
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@data-sync-user @abyrne-moz