-
Notifications
You must be signed in to change notification settings - Fork 13
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
Epic 1115 - Subscriptions #1115
Comments
From ANET advisor training:
|
Proposal of how should "events" be constructed at the first phase of implementation: all lists are chronological, newest first Person: list combining: Position: list combining: Organization: list combining: Task: list combining: Report: not sure yet Authorization group : not sure yet Location My feed: |
This is in preparation for centralising the subscription updates when objects are updated. It also improves the transaction handling. #1115
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Move My Subscriptions to the people Show page.
Perhaps at a later stage, system messages related to change of state of tracked object (i.e. report is approved).
The text was updated successfully, but these errors were encountered: