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.

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

[TAN-1803] New activities endpoint & filtering for management feed #7856

Closed
wants to merge 35 commits into from

Conversation

jinjagit
Copy link
Contributor

@jinjagit jinjagit commented May 10, 2024

WIP

  • Repurposes a redundant index action. Not sure yet if we need a show action.
  • Filters scope first in policy, to just the selected activities that may be shown in the new 'Management Feed'
  • Uses query param filtering by user_ids or project_ids (all 'Management Feed' activities have a relation to user who acted)
  • Introduces a new activity for action: 'changed_publication_status', item_type: ‘Project’
  • Examples of request params in use
  • Examples of responses for each activity type we have selected for the 'Management Feed'

Notes on selected action: 'changed' activities

  • Uses only action: 'changed' activities to cover updates to projects and phases.
    We could produce specific activities per updated attribute (like we already do for phases, here). However, at this point, minimising the number of kinds of activities we use for the Management Feed is probably best.
  • Uses the existing serialized :change attribute to detail the changes to attributes resulting from an update action, in the payload of the 'changed' activities (also with the key :change).
    Re-using the existing :change attribute is probably be simpler for the FE to use, compared to introducing a new :changes (plural) attribute, but this could prove to be wrong.
  • Prevents the creation of a 'changed' activity for a project, when no project attribute has been updated.
    Previously, this could happen when the associated admin_publication.publication_status was changed.
    Now that we use the payload of a 'changed' activity to provide details of the update, this avoids showing a changed activity with no details of any updated attribute(s).

Changelog

Technical

  • [TAN-1803] New activities endpoint & filtering for management feed

@jinjagit jinjagit self-assigned this May 10, 2024
@jinjagit jinjagit marked this pull request as draft May 10, 2024 08:40
@cl-dev-bot
Copy link
Collaborator

cl-dev-bot commented May 10, 2024

Warnings
⚠️ The PR title contains no Jira issue key (case-sensitive)
⚠️ The branch name contains no Jira issue key (case-sensitive)
Messages
📖 Changelog provided 🎉
📖

Run the e2e tests

📖 Check translation progress

Generated by 🚫 dangerJS against 4ac0f29

…pdated

This would happen if only updates to the associated admin_publication
were made. e.g. updating the publication_status
Covers the cases where admin_publication publication_status is
changed, but no published activity would be produced
@jinjagit
Copy link
Contributor Author

Closed, in favor of simpler approach: #7888

@jinjagit jinjagit closed this May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants